Skip to main content
Glama

ARL Protocol

arl_get_job_audit

Read the audit trail of a verified job on Base Mainnet (ARL or USDC escrow): every on-chain event of the job in order (opened, configured, funded, committee approved and accepted, deliverable submitted, votes, verdict, dispute, finalization, payment or refund), each with who acted, the time, the transaction and the hashes it carried. Read at one block that the answer names; an empty trail means the job has no events on the verified evaluator's escrow.

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": {
      "token": "<token>",
      "jobId": "<jobId>"
    },
    "name": "arl_get_job_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob id, decimal
tokenYesThe escrow's payment token

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 full burden and does reasonably well: it discloses that the read is pinned to a single named block (a consistent snapshot), enumerates the event kinds returned, describes per-event fields (actor, time, transaction, hashes), and explains that an empty trail means the job has no events on the verified evaluator's escrow. It omits permission/auth requirements and behavior for a nonexistent or unverified job.

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 sentences, front-loaded with the verb and resource, then the event enumeration, then the block-pinning caveat and empty-result semantics. Dense but every clause carries information an agent needs; no 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 2-parameter read with no annotations and no output schema, the description supplies the equivalent of a return-value summary (event types and per-event fields) plus snapshot and empty-result semantics. Only error/not-found handling and any pagination or size limits are left unaddressed.

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%, so the baseline is 3. The description reinforces that the job must be a verified job and that token selects the escrow ('ARL or USDC escrow'), matching the enum, but adds no format or constraint detail beyond what the schema already documents.

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 and resource ('Read the audit trail of a verified job') and pins the domain (Base Mainnet, ARL or USDC escrow). The enumerated event list (opened, funded, votes, verdict, payment) makes the return scope concrete, though it never names a sibling tool it differs from, so an agent must infer that this is the event-history counterpart to arl_get_job or arl_get_job_receipt.

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: the phrase 'every on-chain event of the job in order' signals this is for full history rather than current state, but there is no explicit 'use this when you need X, use arl_get_job when you need Y' routing. No exclusions or prerequisites (e.g. whether the job must be verified first) 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.

Resources