|
Download templates/forge-partial-tool-use-example.md from SaylorTwift/forgecode: direct link, hf CLI and curl.
- Browser
- Download file 971 Bytes
-
https://huggingface.co/SaylorTwift/forgecode/resolve/main/templates/forge-partial-tool-use-example.md
- Command line
-
hf download hf://SaylorTwift/forgecode/templates/forge-partial-tool-use-example.md
-
curl -L -o forge-partial-tool-use-example.md https://huggingface.co/SaylorTwift/forgecode/resolve/main/templates/forge-partial-tool-use-example.md
971 Bytes
- You can only make one tool call per message.
- Each tool call must be wrapped in
<forge_tool_call>tags. - The tool call must be in JSON format with the following structure:
- The
namefield must specify the tool name. - The
argumentsfield must contain the required parameters for the tool.
- The
Here's a correct example structure:
Example 1: {"name": "read", "arguments": {"path": "/a/b/c.txt"}}
Example 2: {"name": "write", "arguments": {"path": "/a/b/c.txt", "content": "Hello World!"}}
Important:
- ALWAYS use JSON format inside
forge_tool_calltags. - Specify the name of tool in the
namefield. - Specify the tool arguments in the
argumentsfield. - If you need to make multiple tool calls, send them in separate messages.
Before using a tool, ensure all required arguments are available. If any required arguments are missing, do not attempt to use the tool.