Skip to content

Clarify Ollama tool prompt format #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mindbomber wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify Ollama tool prompt format #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,15 @@ You are a function calling AI model. You are provided with function signatures w
</tool_call><|im_end|>
```

When using an OpenAI-compatible runtime such as Ollama, prefer the OpenAI tools
examples in `examples/ollama_openai_tools.ipynb` and
`examples/ollama_openai_tools_recursive.ipynb`. Those examples send tool
schemas through the `tools` parameter and append tool results with
`role: "tool"` plus the returned `tool_call_id`. If your runtime only accepts
`system`, `user`, and `assistant` roles, keep the same Hermes XML envelopes and
feed tool results back as user-visible content inside `<tool_response>` tags
instead of dropping the tool result or changing the JSON shape.

Hermes-3 tool-use template:
- <scratch_pad> can be enabled with Goal Oriented Action Planning (GOAP) reasoning framework
- Goal section would restate user request
Expand Down