github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #9581] YAML file for external web services #52762

New Issue
Closed
opened 2026-04-29 00:47:17 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-29 00:47:17 -05:00
Owner
Copy Link

Originally created by @johnnyainsworth on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9581

I have a number of external web services, for example a search API, that I would like to integrate with the tool calling functionality. Is there any way to set up default tool calling functionality for REST service GET and POST so that all I would need to do is create / edit a yaml file and add the ability to call the web service as a tool from the LLM?

Originally created by @johnnyainsworth on GitHub (Mar 7, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9581 I have a number of external web services, for example a search API, that I would like to integrate with the tool calling functionality. Is there any way to set up default tool calling functionality for REST service GET and POST so that all I would need to do is create / edit a yaml file and add the ability to call the web service as a tool from the LLM?
GiteaMirror added the feature request label 2026-04-29 00:47:17 -05:00
GiteaMirror commented 2026-04-29 00:47:21 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 7, 2025):

You would need to set up an intermediate service or proxy. Your client calls the proxy with a request, the proxy fills in the tools field and sends the request to the ollama server. If it did that you could also have the proxy make the tools calls, and then send the completed response back to your client. The proxy would be configured to read the YAML file to add the appropriate tools calls to the ollama request.

<!-- gh-comment-id:2706736885 --> @rick-github commented on GitHub (Mar 7, 2025): You would need to set up an intermediate service or proxy. Your client calls the proxy with a request, the proxy fills in the `tools` field and sends the request to the ollama server. If it did that you could also have the proxy make the tools calls, and then send the completed response back to your client. The proxy would be configured to read the YAML file to add the appropriate tools calls to the ollama request.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#52762
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?