Skip to main content
Glama

ARL Protocol

arl_get_job_receipt

Read the portable receipt of a finalized verified job on Base Mainnet and prepare the unsigned transaction that records it on the Ethereum Attestation Service (EAS): client, provider and its ERC-8004 agent, the committee's verdict, the deliverable, spec and vote hashes, and when it was finalized. The receipt is null while the job is not finalized. Nothing is signed or sent: attest is for the caller's own wallet (usually the provider, whose record it is), and registerSchema appears while the schema is not on EAS yet.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob id, decimal
tokenYesThe escrow's payment token

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, the description carries the full burden and does well: it declares that nothing is signed or sent, that `attest` targets the caller's own wallet, and that `registerSchema` only appears while the schema is absent from EAS. It omits auth/permission requirements and failure behavior for an unknown jobId or wrong token, which keeps it below the top score.

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?

Purpose and network are front-loaded, and the trailing sentence covers the two conditional output keys efficiently. The colon-delimited field list in the first sentence is dense but each element earns its place; minor tightening possible.

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?

With no output schema and no annotations, the description must carry return-shape information, and it does enumerate the receipt fields, the null case, and the conditional `attest`/`registerSchema` keys. It stops short of saying what the caller should do with the returned unsigned transaction (sign locally? submit where?), which is the main residual 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 coverage is 100% with only two parameters, and the schema already documents jobId as decimal and token as the escrow's payment token with an ARL/USDC enum. The description adds no syntax, format, or meaning beyond that, so the baseline 3 is appropriate.

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 — reading the portable receipt of a finalized verified job on Base Mainnet — and additionally names the second action (preparing the unsigned EAS attestation transaction), plus enumerates the receipt contents. It does not explicitly differentiate itself from arl_get_job or arl_get_job_audit, whose subject matter (verdict, hashes) plausibly overlaps, so the sibling boundary is left implicit.

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 precondition 'The receipt is null while the job is not finalized', which tells the agent when the call yields nothing useful, and by the explanation of what `attest` and `registerSchema` are for. However, there is no explicit guidance on when to pick this tool over arl_get_job or arl_get_job_audit, and no stated prerequisites for the caller.

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.