Skip to main content
Glama

ARL Protocol

arl_get_agent_score

Compute an agent's ARL score (arl-reputation/1) on Base Mainnet from verified outcomes only: the feedback the verified evaluators wrote to the ERC-8004 ReputationRegistry, joined to its jobs, plus jobs the agent took and let expire. score_bps runs from 0 to 10000 and is null below 3 outcomes from 2 distinct clients; each outcome is weighted by budget and age, and no client counts for more than 25 %. Lists the outcomes it used.

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_score"
  }
}

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 supplied, the description carries the full burden and does so well: it discloses the data source, that only verified evaluator feedback and expired jobs count, the score range (0-10000), the null condition (fewer than 3 outcomes from 2 distinct clients), the budget/age weighting, and the 25% per-client cap. Remaining gaps are minor, such as whether the computation is a live read or cached and whether it costs anything.

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 core action, then methodology and output in two compact sentences with no filler. The first sentence is long and clause-heavy, but every clause carries substantive information about the scoring rule.

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 single-parameter read tool with no output schema, the description covers inputs, aggregation rules, edge cases (null below thresholds) and the return shape ('lists the outcomes it used'). Additional detail on staleness or on-chain read behavior would fully close the gap.

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% and the single parameter (agentId, decimal string matching ^[0-9]+$) is fully documented in the schema. The description adds no further meaning about the identifier beyond 'an agent's', so the baseline of 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?

The description names a specific verb and resource (compute an agent's ARL score), pins the chain (Base Mainnet) and the underlying data source (ERC-8004 ReputationRegistry feedback plus expired jobs). It does not explicitly contrast itself with the sibling arl_get_agent_outcomes, though 'Lists the outcomes it used' implies the score is an aggregate rather than a raw listing.

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 rather than stated: an agent can infer this is the tool for a reputation score versus raw outcome retrieval, but there is no explicit when-to-use, when-not, or named alternative. No prerequisites (e.g., whether the agent must exist on-chain) are given.

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.