Agent Data Tools

find_tool

Read-onlyIdempotent

Identify which service tool performs a described job by returning up to ten ranked matches with names, capabilities, prices, and required inputs; use before calling when the tool name is unknown.

Instructions

Find which of this service's 698 tools does a job. Say the job in plain words ("current weather in Paris", "text of a PDF", "is this wallet sanctioned") and get up to ten tools, best match first, each with its name for call_tool, what it does, its price and its required inputs. Free; call it before call_tool whenever you do not already know the tool's name.

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": {
      "need": "<need>"
    },
    "name": "find_tool"
  }
}

Input Schema

Name	Required	Description	Default
`need`	Yes	The job in plain words, for example: current weather in Paris
`count`	No	How many tools to return, 1-10 (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 14, 2026

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description only needs to add what they don't. It does: the call is free, returns at most ten results ordered best-match-first, and each result carries name, description, price and required inputs — fill-in for the missing output schema. Lacks any note on empty or weak-match results, which keeps it just below the top.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it does, what you get back, then the routing rule. The verb and the call-order advice are front-loaded and nothing is repeated from the schema verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return shape (up to ten ranked entries with name, purpose, price, inputs) that an agent otherwise couldn't know. For a two-parameter search tool, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the framing that 'need' should be a plain-language job statement with illustrative examples, and that result volume is capped at ten via the count parameter. That is real meaning beyond the field definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (find) and resource (one of 698 tools) plus the matching criterion (a job in plain words). It is clearly distinguishable from call_tool and tool_details, which it implicitly positions as the follow-up steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call it before call_tool whenever the tool name is unknown, which names the alternative and the condition that selects it. The 'already know the tool's name' clause doubles as the when-not-to-use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server