7Maps

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. To have 7Maps pick one server and tool for you with alternatives, use route.

Input Schema

Name	Required	Description
`job`	Yes	What the tool should do, in plain words, for example "send a transactional email" or "query a postgres database"
`may`	No	What the tool may do: read = read-only only; change = read or change data; any = include high-risk tools (default any)
`limit`	No	How many results (default 10)
`payment`	No	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.
`task_type`	No	Optional: the kind of work you are doing right now. Only this category is kept, never your task text
`agent_model`	No	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
`answering_now`	No	Only servers that answered with tools on the last check (default true)
`max_handshake_ms`	No
`max_tool_list_tokens`	No

Output Schema

Name	Required	Description	Default
`matched`	Yes
`results`	Yes
`tools_indexed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

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"
+}

Changed1 schema field changedOct 6, 2026

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"
+}

AddedOct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, which already mark it as a safe read-only operation, the description discloses the search corpus size and freshness, the result metadata returned (read-only/change/high-risk estimate, server answering status, handshake time, token cost, page link), duplicate collapsing, and that there is no charge. This is unusually rich behavioral context for an agent deciding whether and how to invoke it.

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?

The definition is front-loaded with the core purpose and alternative, and most sentences earn their place by carrying useful selection or behavioral detail. It is dense and somewhat run-on, but not padded or repetitive.

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?

Given the complexity of searching over 200,000 tools and the presence of an output schema, the description is complete enough. It covers the search scope, filters, return-value highlights, deduplication behavior, cost, and the routing alternative that an agent needs to call it correctly.

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 78%, so the schema already documents most parameters well. The description adds some filter semantics by mentioning read-only tools, servers answering now, and latency or token ceilings, but it does not add meaning beyond the schema for parameters like job, limit, payment, task_type, or agent_model. Baseline 3 is appropriate given the high schema coverage.

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?

The description states a specific verb and resource: search every tool on every public MCP server on the 7Maps map to find a tool for a job. It clearly distinguishes this broad-discovery tool from the sibling routing tool 'route', which picks one server and tool for the agent.

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?

It explicitly says when to use this tool: 'when you need a tool for a job and do not know which MCP server has one.' It also names the alternative ('route') and the condition that selects it, leaving little ambiguity about tool choice.

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

All 7Maps tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?