Skip to main content
Glama

moltrust_erc8004

Read-only

Query the ERC-8004 on-chain agent registry on Base to resolve MolTrust agents, fetch Agent Cards, and look up on-chain agents by agentId.

Instructions

Query the ERC-8004 on-chain agent registry on Base.

Resolve MolTrust agents to their on-chain ERC-8004 identity, fetch Agent Cards, or look up on-chain agents by their agentId.

Args: action: One of "card", "resolve", or "well-known" did: Agent DID (required for "card", e.g. "did:moltrust:a1b2c3d4e5f60718") agent_id: On-chain ERC-8004 agent ID (required for "resolve", e.g. 21023)

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": {
      "action": "<action>"
    },
    "name": "moltrust_erc8004"
  }
}

Input Schema

NameRequiredDescriptionDefault
didNoAgent DID (required for "card", e.g. "did:moltrust:a1b2c3d4e5f60718")
actionYesOne of "card", "resolve", or "well-known"
agent_idNoOn-chain ERC-8004 agent ID (required for "resolve", e.g. 21023)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.1
    • addedInput schema / properties / action / description
      Added value: +"One of \"card\", \"resolve\", or \"well-known\""
    • addedInput schema / properties / agent_id / description
      Added value: +"On-chain ERC-8004 agent ID (required for \"resolve\", e.g. 21023)"
    • addedInput schema / properties / did / description
      Added value: +"Agent DID (required for \"card\", e.g. \"did:moltrust:a1b2c3d4e5f60718\")"
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true is consistent with a 'Query' tool and the description adds useful context not in the annotations: the registry is on-chain on Base and has three distinct resolution modes. However, it says nothing about what happens for an unregistered DID or unknown agentId (error vs. empty result), nor about latency or rate limits on chain lookups. With annotations covering the safety profile, this partial behavioral context earns a 3.

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 purpose is front-loaded in a single line, followed by the mode list and a compact args block. The args block duplicates the schema verbatim, which is wasted text, but nothing else is padded.

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

Completeness3/5

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

An output schema exists so return values need not be explained, and all three parameters are documented. The notable gap is that the third action, 'well-known', is enumerated but never described — an agent cannot tell what it does or which parameters it needs (the args list only mentions card and resolve). That leaves one of three modes under-specified.

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 description coverage is 100%, so the baseline is 3; the description goes slightly further by pairing each parameter with the action that requires it and giving example formats (did:moltrust:a1b2c3d4e5f60718, agentId 21023). It largely restates the schema, but the action-parameter coupling is a genuinely useful cross-parameter constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb and resource — querying the ERC-8004 on-chain agent registry on Base — and the second sentence enumerates the three operations (resolve, fetch Agent Cards, look up by agentId). It is distinguishable from registry-adjacent siblings by domain, but it never names an alternative tool, so routing still requires inference.

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?

The action-to-parameter mapping (card needs did, resolve needs agent_id) implies how to invoke each mode, but there is no explicit statement of when to choose this tool over moltrust_verify or moltrust_reputation, and no stated preconditions. Usage is inferable rather than guided.

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