7Maps

Resolve a job to MCP servers (signed)

resolve

Read-onlyIdempotent

Use this when you need an MCP server for a job and want a signed, expiring answer you can verify: returns up to 10 servers that answered at their last check, each with a stable ID, its address, its status, when it was checked and an Ed25519 signature (JWS) valid for 48 hours. The keys are at https://7it.co.il/.well-known/capability-resolver. It never connects you to a server; your client decides. No charge.

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

Input Schema

Name	Required	Description
`need`	Yes	The job in plain words, for example "send a transactional email"
`max_ms`	No	Only servers whose handshake took at most this long
`payment`	No	none = only servers that declare no payment
`read_only`	No	Only servers with a read-only tool for the job
`no_sign_in`	No	Only servers that answered without sign-in

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: caps results at 10, enumerates the returned fields (stable ID, address, status, check time, Ed25519 JWS), states the 48-hour validity, gives the key-discovery URL, and explicitly says it never connects you to a server. The "no charge" note and the 48h expiry are exactly the kind of operational context annotations cannot carry.

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 usage trigger and zero filler; the trailing two sentences (key URL, no connection, no charge) are short and purposeful. The middle sentence is a dense run-on packing many clauses, which slightly hurts scannability.

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 carries the return-value burden and does so completely: field list, signature scheme, expiry, and key location. Combined with the fully documented input schema and safety annotations, an agent has everything needed to call and interpret this tool.

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 100%, so every one of the five parameters is already documented in the schema. The description adds only indirect meaning ("answered at their last check", "up to 10") without explaining filters like max_ms, read_only, or no_sign_in. Baseline 3 is correct.

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 (resolve) and resource (a job to MCP servers) plus the distinguishing property — a signed, expiring answer. An agent can tell this apart from find_tool or preflight without opening any schema.

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

Usage Guidelines4/5

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

"Use this when you need an MCP server for a job and want a signed, expiring answer you can verify" gives a clear triggering condition. It stops short of naming alternatives among siblings (find_tool, preflight) or stating when not to use it, so routing is implied rather than explicit.

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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?