Skip to main content
Glama
Sign In
ERC-8004 MCP Server

ERC-8004 MCP Server

by wpank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

erc8004_get_agent

Read-only

Get full details for an ERC-8004 agent by ID, including contract state, services, metadata, statistics, and feedback.

Instructions

Get full details for a specific ERC-8004 agent by ID, including contract state, services, metadata, statistics, and recent feedback.

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": {
      "agentId": "<agentId>"
    },
    "name": "erc8004_get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe agent's subgraph entity ID (e.g., '11155111:1213')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds value by specifying the scope of returned data (contract state, services, etc.). No behavioral traits beyond read-only are mentioned, but annotations cover the main safety profile.

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?

A single sentence that front-loads the purpose and then lists included details. Every word contributes meaning with no redundancy.

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-only tool with no output schema, the description sufficiently covers what the tool returns by listing categories. Given annotations handle safety, no further context is needed.

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?

The input schema already describes the single parameter 'agentId' with an example format ('11155111:1213'). The description adds no additional semantic information beyond what the schema provides.

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 clearly states the tool's purpose: retrieving full details for a specific ERC-8004 agent by ID, listing included categories (contract state, services, metadata, statistics, feedback). This distinguishes it from sibling tools that focus on single aspects.

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?

No explicit when-to-use or when-not-to-use guidance. The description implies usage via agent ID but does not mention alternatives or conditions for using this tool over narrower siblings like erc8004_get_agent_feedback.

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

Deploy Server

Other Tools