add README.md
Browse files
README.md
ADDED
|
@@ -0,0 +1,26 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# ToolACE (tool-calling conversations)
|
| 2 |
+
|
| 3 |
+
A cleaned-up mirror of the ToolACE function-calling corpus. Every line of
|
| 4 |
+
`data/train.jsonl` is one JSON object describing a full conversation.
|
| 5 |
+
|
| 6 |
+
## Entry format
|
| 7 |
+
|
| 8 |
+
- `messages`: list of turns.
|
| 9 |
+
- The first message is always a `system` message with boilerplate about how
|
| 10 |
+
to use tools (the tool definitions themselves are NOT embedded there).
|
| 11 |
+
- Assistant messages that invoke tools carry `tool_calls`: a list of
|
| 12 |
+
`{id, type: "function", function: {name, arguments}}` objects, where
|
| 13 |
+
`arguments` is already a JSON object (not a string).
|
| 14 |
+
- Tool results come back as `{role: "tool", tool_call_id, content}` messages,
|
| 15 |
+
where `tool_call_id` references the originating call.
|
| 16 |
+
- `tools`: list of tool definitions, each with `name`, `description` and
|
| 17 |
+
`parameters`. `parameters` is an object with `type` (`dict` for object
|
| 18 |
+
containers), `properties` (parameter name -> `{type, description}` plus an
|
| 19 |
+
optional `default`) and `required`. Parameter types use the short spellings
|
| 20 |
+
`str`, `int`, `float`, `bool`, `list`, `dict`.
|
| 21 |
+
|
| 22 |
+
## Files
|
| 23 |
+
|
| 24 |
+
- `data/train.jsonl` - all examples.
|
| 25 |
+
|
| 26 |
+
Total examples: 30
|