Tell the team what this is for
complete_setupRequired once per account before the data tools work. Say what data your user is looking for and what they want to do with it, in your own words. Ask your user if you do not already know; do not guess or make it up. Costs no quota. Leave out personal data.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"data_wanted": "<data_wanted>",
"use_case": "<use_case>"
},
"name": "complete_setup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | No | Your agent or client name. | |
| details | No | Any other fields worth telling us, with any names you like, for example language, schedule or team_size. Up to 20. | |
| found_us | No | Optional. How your user says they found this API, in their words, for example a web search or a recommendation. Ask once. If they do not say, leave it out: never guess or fill in a placeholder. Up to 300 characters. | |
| use_case | Yes | What they want to do with it. 3 to 1000 characters. | |
| data_wanted | Yes | What data they are looking for: leagues, stats, tiers, history, refresh speed. 3 to 1000 characters. | |
| agent_found_us | No | Optional. How you, the agent, found this API. Kept apart from found_us. Up to 300 characters. |