Skip to main content
Glama

ARL Protocol

arl_get_job

Read a verified job on the ARL escrow (ARL or USDC) on Base Mainnet: status, client, provider, budget, deadline, committee configuration and the committee's verdict, all at one block that the answer names.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob id, decimal
tokenYesThe escrow's payment token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this is a read operation and adds a real behavioral guarantee: every returned field is consistent at a single named block. It does not say whether the answer reverts or errors for a nonexistent jobId, whether there are auth requirements, or what the response shape looks like beyond the field list.

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?

It is a single front-loaded sentence that opens with the verb and the resource. The field enumeration earns its place by substituting for a missing output schema. The trailing clause 'all at one block that the answer names' is slightly cryptic, but it carries a real consistency guarantee.

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?

Because there is no output schema, the description correctly compensates by enumerating the returned fields and adding a consistency guarantee. The remaining gaps are error and edge-case behavior for an unknown jobId, plus missing guidance on when to prefer this over the audit and receipt siblings.

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 shape of both parameters is already documented; the description only reinforces the token values ('ARL or USDC') and adds chain context ('Base Mainnet'). It adds no detail beyond the schema about the jobId format. Baseline of 3 is appropriate when the schema does the heavy lifting.

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?

The description uses a precise verb ('Read') and a specific resource ('a verified job on the ARL escrow (ARL or USDC) on Base Mainnet') and then lists the returned fields (status, client, provider, budget, deadline, committee configuration, verdict). That tells an agent exactly what this does and distinguishes it from siblings such as arl_get_job_audit and arl_get_job_receipt. It does not explicitly say how this differs from those siblings, which is why it does not earn a 5.

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 intended usage is only implied: the description conveys 'inspect the state of a job' and hints at a point-in-time snapshot ('all at one block that the answer names'), but never says when to call this tool versus the audit, receipt, or trust-graph siblings. There are no when-not-to-call notes and no prerequisites.

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