Skip to main content
Glama

TOLLA Network

ERC-8004 agents

lookup_agent
Read-onlyIdempotent

Look up AI agents in the ERC-8004 identity registry on Robinhood Chain by agent id, owner address or 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": {
      "query": "<query>"
    },
    "name": "lookup_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAgent id (number), owner 0x address, or part of a name or host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the registry and chain scope, but says nothing about whether a partial-name query returns one or many matches, whether results are paginated, or what the response contains — the main real behavioral unknown for a lookup tool.

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?

One front-loaded sentence that packs verb, registry, chain and accepted keys with no filler. Nothing can be removed without losing information.

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 single-parameter read-only lookup with full schema coverage and annotations, the description covers what to search and where. Only the multi-result / partial-match behavior is left unstated, which is a minor residue for this complexity level.

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?

A single required parameter with 100% schema coverage, so the schema carries the burden; the description independently restates the three accepted input forms (id, owner address, name). It is slightly narrower than the schema, which also allows a host fragment, but that overlap is additive rather than misleading.

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?

Specific verb ("Look up"), specific resource ("AI agents in the ERC-8004 identity registry on Robinhood Chain"), and it enumerates the three addressing keys. An agent knows exactly what domain this touches and needs no other tool to infer it.

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

Usage Guidelines3/5

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

Usage is only implied by the description: it is clearly the lookup entry point for ERC-8004 agents, but there is no statement of when to prefer it over siblings, no prerequisite, and no exclusion. No sibling covers agent resolution, so the gap is mild rather than harmful.

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