Skip to main content
Glama

Get agent

get_agent
Read-onlyIdempotent

Details of one agent: each declared endpoint with lcas's check result, 30-day history and all-time working days, since when the current owner holds it, the weekly live test where one exists (one read-only tool called, or one skill example sent), its MCP tools or A2A skills, copies, feedback counts per tag, and money hints (tools that move funds, payment asked, owner wallet kind: wallet, Safe multisig or contract).

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

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe agent's token ID in the ERC-8004 Identity registry.
chain_idYes1 = Ethereum, 8453 = Base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description rightly focuses elsewhere. It adds real context about payload shape (30-day history, all-time working days, owner tenure, live-test details, money hints), but says nothing about failure behavior for an unknown agent_id/chain_id, result size, or latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every clause carries distinct return-value information, so there is little pure filler, but it is delivered as one ~80-word run-on after a colon with no grouping or hierarchy, which makes it hard to scan. Purpose is front-loaded correctly.

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?

With no output schema, the description is the sole source of return-value information and it covers that thoroughly, including the specialised 'money hints' and 'lcas check result' concepts. The main gap is the absence of any note on what happens when the agent does not exist or the chain_id is unsupported.

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?

Schema description coverage is 100% — agent_id is documented as an ERC-8004 token ID with a numeric pattern and chain_id enumerates 1=Ethereum, 8453=Base. The description adds nothing about either parameter, which is acceptable given the schema does the work, but no extra meaning is contributed.

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 clause 'Details of one agent' plus the required chain_id/agent_id make it unambiguous that this is a single-agent lookup, and the enumerated payload (endpoints, check results, history, ownership, live test, tools/skills, copies, feedback, money hints) tells the agent what makes it different from a search result. It never names a sibling, so differentiation is inferred rather than stated.

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 guidance on when to reach for this versus search_agents, check_agent, or find_tools, and no stated prerequisites (e.g. needing a known agent_id from a prior search). The only usage signal is implicit in 'one agent'.

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