Skip to main content
Glama

Find an MCP tool for a job (7Maps)

find_tool
Read-onlyIdempotent

Use this when you need a tool for a job and do not know which MCP server has one: searches every tool of every public MCP server on the 7Maps map (over 200,000 tools, probed daily) and returns the best matches with an automated estimate of what each tool can do (read-only, changes data, high risk), whether its server is answering now, its handshake time, the tokens its tool list costs to load, and a page to check it. Filter to read-only tools, servers answering now, a latency or token ceiling. Copies of the same tool on several servers are collapsed. No charge. Which to use: find_tool searches tools yourself; route has 7Maps pick and rank servers for a task; resolve returns a signed list a client can verify.

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": "find_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesWhat the tool should do, in plain words, for example "send a transactional email" or "query a postgres database"
mayNoWhat the tool may do: read = read-only only; change = read or change data; any = include high-risk tools (default any)
limitNoHow many results (default 10)
paymentNoPayment terms: any (default); free_only = only servers that declare no payment; paid_ok = servers that charge are fine, servers whose payment terms are unknown are left out. Paid servers show their declared price per call.
last_tripNoOptional: {server, tool, ok, ms} of your previous MCP server call
task_typeNoOptional: kind of work (only the category is kept)
agent_modelNoOptional: your model id, e.g. "claude-sonnet-5-5". Anonymous
answering_nowNoOnly servers that answered with tools on the last check (default true)
max_handshake_msNo
max_tool_list_tokensNo

Output Schema

NameRequiredDescriptionDefault
matchedYes
resultsYes
tools_indexedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / agent_model / description
      Previous value: -"Optional: the model you run on, for example \"claude-sonnet-5-5\", \"gpt-5\", \"llama3.2:3b\". Anonymous; it helps 7Maps learn which servers work for which models"New value: +"Optional: your model id, e.g. \"claude-sonnet-5-5\". Anonymous"
    • changedInput schema / properties / task_type / description
      Previous value: -"Optional: the kind of work you are doing right now. Only this category is kept, never your task text"New value: +"Optional: kind of work (only the category is kept)"
  2. Changed1 schema field changed
    • addedInput schema / properties / last_trip
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Optional: {server, tool, ok, ms} of your previous MCP server call",
      +  "properties": {},
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / agent_model
      Added value: +{
      +  "description": "Optional: the model you run on, for example \"claude-sonnet-5-5\", \"gpt-5\", \"llama3.2:3b\". Anonymous; it helps 7Maps learn which servers work for which models",
      +  "maxLength": 80,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_type
      Added value: +{
      +  "description": "Optional: the kind of work you are doing right now. Only this category is kept, never your task text",
      +  "enum": [
      +    "coding",
      +    "research",
      +    "data",
      +    "communication",
      +    "commerce",
      +    "devops",
      +    "content",
      +    "personal_assistant",
      +    "testing",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / payment
      Added value: +{
      +  "description": "Payment terms: any (default); free_only = only servers that declare no payment; paid_ok = servers that charge are fine, servers whose payment terms are unknown are left out. Paid servers show their declared price per call.",
      +  "enum": [
      +    "any",
      +    "free_only",
      +    "paid_ok"
      +  ],
      +  "type": "string"
      +}
  5. Added

TDQS

A4.3/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. The description adds substantive context beyond them: coverage scale and refresh cadence, daily probing, deduplication of identical tools across servers, per-result risk estimates, server liveness and handshake timing, token cost of loading a tool list, and that the call is free. It stops short of describing ranking behavior or failure/empty-result semantics.

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

Conciseness4/5

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

Front-loaded with the trigger, then coverage, then the enumerated result payload, then the routing sentence — a sensible order. It is one dense paragraph and spends a clause enumerating return fields that the output schema already specifies, which is modest redundancy rather than bloat.

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

Completeness4/5

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

For a 10-parameter, open-ended search tool with an output schema, the description supplies the decision context an agent needs: trigger, alternatives, filters, dedupe behavior, and cost. Minor gaps remain around ranking/relevance behavior and what an empty or low-confidence result means.

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

Parameters3/5

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

Schema description coverage is 80%, so the schema already documents job, may, limit, payment, task_type, agent_model, answering_now, and the two ceilings. The description only restates the filters collectively ('read-only tools, servers answering now, a latency or token ceiling') without adding format or interaction detail beyond the schema.

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 and resource: it searches every tool across every public MCP server on the 7Maps map and returns ranked matches. The scope (200,000+ tools, probed daily) and the fact it searches tools directly, not servers, make it readily distinguishable from route and resolve.

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?

Gives an explicit trigger ('when you need a tool for a job and do not know which MCP server has one') and then a dedicated 'Which to use' sentence contrasting find_tool with route and resolve. Both the when and the alternatives are stated rather than implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources