Skip to main content
Glama

ARL Protocol

arl_get_agent

Read an agent's passport on Base Mainnet: who the ERC-8004 agent is (registered or not, owner, and the name and description its owner states in the registration file, which are untrusted text) and what it has verifiably done (its arl-reputation/1 score, its verified outcomes and when the first and latest were). Read at one block that the answer names.

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": "arl_get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesERC-8004 agent id, decimal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does add real context: reads are pinned to a single block named in the answer, and the owner-supplied name/description are flagged as untrusted text. It still omits permission/auth requirements, what happens on an invalid or unknown agent id, and whether the outcome list is bounded or paginated.

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?

Front-loaded with the verb and subject, and every clause carries information — the untrusted-text caveat and the single-block read are both worth their words. It is one dense sentence, so the identity portion and the reputation portion could be split for easier scanning.

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 one-parameter read tool with no output schema, the description adequately previews the returned fields and their provenance, which is what an agent needs to decide whether to call it. Remaining gaps are secondary: the shape of the outcomes list and error behavior for unregistered or malformed ids.

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 single agentId parameter is fully documented in the schema (100% coverage, decimal pattern for an ERC-8004 id), so the schema does the work and the description adds nothing about the id format. The 'one block that the answer names' phrasing describes read semantics, not a parameter, and risks being misread as an input.

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?

Specific verb (Read) plus resource (an agent's passport on Base Mainnet), and it enumerates the exact payload: registration status, owner, owner-stated name/description, arl-reputation/1 score, verified outcomes and their first/latest timestamps. The enumeration implicitly separates it from the narrower arl_get_agent_score and arl_get_agent_outcomes siblings, though no sibling is named explicitly.

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: an agent can infer this is the full-profile read versus the score-only or outcomes-only siblings, but the description never states when to choose it over them or when not to use it. No prerequisites, no fallback path for unregistered agents beyond a passing parenthetical.

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.