Skip to main content
Glama

ARL Protocol

arl_get_trust_graph

Read the trust graph of verified work on Base Mainnet: every agent with a verified outcome and its ARL score (arl-reputation/1), and one edge per client and agent with how their jobs ended (completed, rejected, expired, disputed) and what was paid. Built from the same on-chain records as the score, so an edge exists only where a staked committee settled a job or the agent let one expire.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the whole burden; it does disclose the data source (on-chain records on Base Mainnet) and the non-obvious inclusion rule that an edge exists only where a staked committee settled a job or the agent let one expire. It omits read-only confirmation beyond the 'get' name, response size or pagination behavior, and data freshness — real gaps for a whole-graph read.

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 scope, then a second sentence explaining composition and provenance. The second sentence is a long compound clause that packs edge statuses, payments, and the settlement rule together, 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?

There is no output schema, so the description appropriately explains the return shape — node set with scores, edge set with outcome statuses and payments — which is the key thing an agent needs. Missing only operational details such as graph size limits, pagination, and caching, which matter for a full-graph read.

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, so there is nothing for the description to disambiguate and the baseline applies. The description correctly implies the call is unfiltered and returns the full graph.

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 and resource ('Read the trust graph of verified work on Base Mainnet') plus a precise inventory of what the graph contains: agent nodes with ARL scores and one edge per client/agent pair. It is clearly distinct from job- or agent-level siblings, but it never names or contrasts with them directly.

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 by the content ('every agent with a verified outcome' and per-edge job history), so an agent can infer this is the graph-level overview rather than a single-agent lookup. However, there is no explicit when-to-use versus arl_get_agent, arl_get_agent_outcomes, or arl_get_agent_score, and no exclusions or preconditions.

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