Skip to main content
Glama

ARL Protocol

arl_list_validators

List the validators of the verified evaluators on Base Mainnet: every address that staked, its stake and the part locked as bonds on running jobs (base units of the stake token), the jobs it accepted, its votes by direction, its slashes, and since when it has staked. Anyone can stake and be named on a committee; this is the record to read before naming one. Read at one block that the answer names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arl_list_validators"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 it does substantial work: it discloses that stake figures are in base units of the stake token, that part of stake is locked as bonds on running jobs, and that validator status is permissionless rather than an endorsement. "Read at one block that the answer names" communicates block-pinning consistency semantics that an agent could not infer otherwise. Remaining gaps are ordering, size, and address formatting.

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?

Verb and resource are front-loaded, and the two follow-up sentences each add distinct value (usage rationale, block semantics). The middle sentence is a dense comma-chained enumeration of returned fields that would read more cleanly as a list, but no sentence is filler.

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 zero-parameter, output-schema-less tool, the description is the only source of return-shape information and it supplies it field by field, plus units and a block-consistency caveat. Minor omissions remain: result ordering, approximate result size, and whether addresses are checksummed or labeled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; the description adds no parameter guidance because none is needed. The block-consistency note describes the response, not an argument, so it does not change this score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the validators of the verified evaluators on Base Mainnet") and then enumerates the exact record contents: stake, bonded portion locked on running jobs in base units, accepted jobs, votes by direction, slashes, and staking start time. This clearly separates it from singular-entity siblings like arl_get_agent or arl_get_agent_score.

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

Usage Guidelines4/5

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

"This is the record to read before naming one" gives an explicit decision point for committee selection, and the preceding sentence explains why the record matters (anyone can stake and be named). It does not name a specific alternative tool to use instead when a single agent's status is needed, so it falls short of full when/when-not routing.

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