Découverte d'outils

Rechercher, lister et décrire chaque outil de ce catalogue, ou en appeler un par son nom — utile pour un client qui préfère une liste d'outils compacte plutôt que de tous les charger.

• Readsearch_os_toolsSearch for the most relevant OS tools by plain-language description of what you want to do. Matches by keyword against every registered tool's name and description, not by meaning — results are strongest when your query shares words with the tool's name or description (e.g. "reply to a review", "boost a post", "team member"). Returns up to `limit` results in relevance order, most relevant first — there's no relevance cutoff, so a result appearing here means it scored above zero, not that it's necessarily a good match; use judgment, and fall back to list_os_tools to browse by domain if nothing here looks right. Once you've found a name, call describe_os_tool(name) for its full schema, then call_os_tool(name, arguments) to run it.
• Readlist_os_toolsList every registered OS tool grouped by domain — name + one-line description only, built live from the actual tool registry (never a static/hardcoded list, so it can't go stale). Use this when search_os_tools comes up empty, or when you know the domain but not the exact tool name. Call describe_os_tool(name) for a specific tool's full input schema.
• Readdescribe_os_toolGet the full description, input schema, and mutation/scope metadata for one tool by exact name. Use this after search_os_tools or list_os_tools has identified a candidate, before calling call_os_tool.
• Readdescribe_os_toolsBulk form of describe_os_tool: get the full schema for MANY tools in ONE call. Pass `names` (array of exact tool names) or omit it to get every registered tool. Prefer this over looping describe_os_tool when you need more than a couple of schemas — each describe is a network round trip, and this collapses N of them into one.
• Writecall_os_toolExecute any real OS tool by exact name with the given arguments — the actual invocation path for every tool discovered via search_os_tools/list_os_tools/describe_os_tool. Subject to the exact same policy checks as calling the tool directly (including the read-only guard, when active) — this is a proxy, not a bypass.