Skip to main content
Glama
Sign In
aiden-mcp

aiden-mcp

Official
by aiden-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get agent

get_agent
Read-onlyIdempotent

Retrieve the full AIDEN record for an ERC-8004 agent by ID, covering profile, owner, wallet, reputation, validations, trust score, and USDG settlement evidence.

Instructions

Full AIDEN record for one agent: profile, owner, agent wallet, reputation summary, validations, trust score and the USDG settlement evidence behind it.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesERC-8004 agent ID (token ID in the Identity Registry)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. With no output schema, the description usefully discloses what the returned record contains (including 'USDG settlement evidence'), which the annotations cannot convey. It stops short of noting freshness, caching, or error behavior for an unknown agent_id.

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 front-loaded sentence with no filler; the colon-delimited field list is the most compact way to convey record scope. Every clause earns its place.

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?

Given absent output schema, the description compensates by enumerating the record's contents, and the annotations carry the safety profile. Adequate for a one-parameter lookup, though it omits what happens for a nonexistent or malformed agent ID.

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?

One parameter with 100% schema description coverage; the schema already explains that agent_id is the ERC-8004 agent ID (token ID in the Identity Registry). The description adds no format, range, or lookup guidance beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Full AIDEN record for one agent') and enumerates the record contents — profile, owner, wallet, reputation, validations, trust score, settlement evidence. That enumeration implies it is the superset of get_agent_feedback and get_agent_validations, but those siblings are never named, so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus search_agents or the narrower get_agent_feedback / get_agent_validations calls. The 'full record' framing hints at usage but gives no conditions, prerequisites, or exclusions.

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