概要

Find tool

MCPfind_tool
READ
Features

Search this server's own tool catalog by what you're trying to do, in your own words — not a guessed tool name. On a customer's own token this is what surfaces the tools this connection can already call but tools/list does not spell out one by one: the webhook alert registrars ('notify us when traffic drops'), giving a finished site away, changing who may SEE the site. The documentation tools themselves — branding, navigation, domain, languages, translations, the chat assistant, conversion goals, and writing the pages — are in tools/list directly since 2026-09-22, so call those by name without searching first. call: "direct" is a name your client already lists: call it by name. call: "call_tool" is one it does not: run it as call_tool { name, arguments } — calling such a name directly fails INSIDE YOUR OWN CLIENT ('no such tool'), before the request ever reaches this server, because a client builds what it may call out of tools/list. Each match carries accepts — the fields that name takes — so the call_tool arguments can be built from this answer alone. This tool runs nothing itself. Returns matching names with a trimmed description and the family each belongs to; get_info gives the family overview when the query itself does not narrow it down.

Input2
querystringrequired
What you are trying to do, in natural language — a question or a sentence, not keywords.
limitinteger
Max results (default 8).
Limitations
  • 🔴 EVERY MATCH SAYS HOW TO CALL IT, and the two ways are not interchangeable.
Example input
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_tool",
    "arguments": {
      "query": "<query>"
    }
  }
}

更新日

このページは役に立ちましたか?