Skip to main content
Glama

Find an agent

find_agent
Read-onlyIdempotent

Use this to look up one or many agents by id, name or wallet; agent_record gives one ranked agent's full record. Look up an ERC-8004 agent by token id on Base, slug, wallet address (0x...) or the name it declares. Returns whether it is ranked, its liveness level (L0-L9), bound wallet, stablecoin float, payment totals and open incidents. Up to 25 ids at once, separated by commas. A name is matched among ranked agents only, and a declared name is the agent's own claim, not verified.

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": {
      "query": "<query>"
    },
    "name": "find_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesToken id (57657), slug (8004-base-57657), wallet (0x...), a declared name, or up to 25 ids separated by commas

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Token id (e.g. 57657), slug (8004-base-57657) or wallet address (0x...)"New value: +"Token id (57657), slug (8004-base-57657), wallet (0x...), a declared name, or up to 25 ids separated by commas"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), and the description goes further with concrete operating constraints: a 25-id batch cap, comma-separated syntax, and the important caveat that a declared name is the agent's own unverified claim. It also lists what the result surfaces (ranked status, liveness L0-L9, bound wallet, float, payment totals, incidents), which is essential since there is no output schema.

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 primary use case and the sibling disambiguation in the first sentence, with caveats placed last where they belong. The opening "Use this to look up..." and the following "Look up an ERC-8004 agent..." restate the same action, a small redundancy that keeps it from a 5.

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?

For a single-parameter read tool with no output schema, the description carries exactly the missing burden: what fields come back, the batch limit, the accepted identifier formats, and the trust caveat on declared names. Nothing an agent needs in order to call this correctly is absent.

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% and the single parameter is already documented with examples, so the baseline is 3. The description adds value beyond it by disclosing the 25-id batching behavior and the ranked-only restriction on name matching, which are semantics the schema itself does not state.

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 ("look up one or many agents") plus the accepted identifier space, and explicitly contrasts itself with sibling agent_record ("agent_record gives one ranked agent's full record"). An agent can distinguish this bulk lookup from the single-record sibling without opening either 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?

Names the alternative (agent_record) and states the condition that would select it, and adds a real scope constraint that governs whether a lookup will succeed ("A name is matched among ranked agents only"). It does not enumerate when-not-to-use cases beyond that, so it falls just short of a full 5.

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.