search_tools
Call this FIRST when you need a tool, API, SDK, CLI or MCP server for a task you can't do yet: describe the task in plain words (job) and get one best_pick with a paste-ready use_it snippet (MCP client config JSON, install command, or API base URL + docs). One call is usually enough: best_pick.summary says in one line what to use and why (reasons: vendor-official or third-party, live check, auth, read-only or can send/spend, outcome reports), best_pick.report_call is the one-line report to send after you use it; results lists ranked alternatives with score breakdowns (evidence, source URL, date), side effects and human steps; verdict is honest (good_match / weak_matches / nothing_good_found / cannot_work_as_asked / not_a_tool_job, then best_pick is null and answer says why; not_a_tool_job adds a curated workaround). Constraints written in the job ('no account', 'nothing paid', 'no new token scopes', 'headless') or in constraints are checked per result (constraint_check). Free, no key. Returns a top-level report_token for optional feedback.
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": {
"job": "<job>"
},
"name": "search_tools"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | Yes | The task in plain words, e.g. 'send SMS to customers', 'read my Google Calendar', 'GitHub MCP server' | |
| stage | No | optional, self-declared | |
| client | No | optional, e.g. claude-code, cursor, my-agent | |
| detail | No | brief drops per-result score_breakdown and why[] (about 4x smaller); default full | |
| agent_type | No | optional, self-declared | |
| constraints | No | ||
| watcher_key | No | optional: get an alert if nothing good is found now but a match appears later |