Skip to main content
Glama

ARL Protocol

arl_check_evidence

Check an arl-evidence/2 package offline: that the on-chain settlement record, the task, the proof and the policy agree. Returns the outcome and the vote counts.

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": {
      "evidence": "<evidence>"
    },
    "name": "arl_check_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidenceYesAn arl-evidence/2 document

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful traits: the check is offline, it validates agreement across four artifacts, and it returns an outcome plus vote counts. It stops short of saying whether a failed check raises an error or returns a negative outcome, and does not state that it is side-effect free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the operation and its scope come first, the return values second. There is no filler and nothing an agent must read past to find the core action.

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 tool taking a nested evidence document with no output schema, the description covers the verification scope and gives a brief sketch of the return values (outcome and vote counts). A short note on failure behavior would close the remaining 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 there is a single required parameter documented as "An arl-evidence/2 document", so the baseline is 3. The description reinforces the format name ("arl-evidence/2 package") but adds no structural detail beyond the schema.

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?

States a specific verb ("Check") and a specific resource (an arl-evidence/2 package), then enumerates exactly what is being cross-validated: the on-chain settlement record, the task, the proof and the policy. It is distinguishable from siblings like arl_check_task, though it never explicitly contrasts itself with them.

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?

The word "offline" implies the tool is for local verification of an evidence bundle without network round-trips, which hints at when to reach for it, but there is no explicit when-to-use or when-not-to-use guidance relative to arl_check_task or the arl_get_* family. The agent must infer the routing decision.

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