Skip to main content
Glama

ARL Protocol

arl_get_agent_outcomes

Read an agent's verified record on Base Mainnet: how many of its jobs the ARL and the USDC verified evaluators approved and rejected. The evaluators keep these counts themselves (outcomesOf), so a reputation registry refusing a write cannot erase them. 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_outcomes"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesERC-8004 agent id, decimal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the chain (Base Mainnet), the data source (evaluators store counts via outcomesOf), an immutability property (registry write refusal cannot erase them), and a block-consistency constraint ("Read at one block that the answer names"). It stops short of explaining return shape, rate limits, or authentication.

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?

Three sentences, front-loaded with the action and resource, then the trust rationale, then the block-consistency note. Each sentence adds information, though the final phrase "Read at one block that the answer names" is slightly cryptic and could be clearer.

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 simple one-parameter read with no output schema, the description explains what is returned conceptually (approved and rejected counts from two evaluator sources), why the data is trustworthy, and the block-consistency behavior. Missing only the precise return structure and any access constraints.

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 coverage is 100% and the sole agentId parameter is fully documented in the schema as an ERC-8004 decimal id. The description adds no meaning about agentId itself; its block-consistency sentence refers to how the read is pinned, not to any input parameter.

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 description states a specific verb and resource: "Read an agent's verified record on Base Mainnet" and specifies the content as approved/rejected job counts from ARL and USDC verified evaluators. It is clearly an outcome-counts read, but it does not explicitly differentiate itself from sibling reads such as arl_get_agent_score or arl_get_agent.

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 implied through the trust model: these counts are kept by evaluators themselves and survive a registry refusing a write, which suggests preferring this over registry-derived reputation when write-refusal resistance matters. However, no explicit when-to-use or when-not-to-use guidance, and no sibling alternative is named.

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