Skip to main content
Glama

Get an escrow job's status

get_escrow_job
Read-onlyIdempotent

Reads one escrow job from Base Mainnet and AgentSLA's records: status (active, settled or reclaimed), creator, provider, listing and endpoint, price, fee, registered latency limit, created time, and when the creator may reclaim it if the oracle has not settled it. Use it after register_escrow_terms to follow a job to completion. Free and read-only.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesEscrow job id, returned by register_escrow_terms, e.g. 2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so 'Free and read-only' mostly restates them. The genuinely additive detail is the data provenance (Base Mainnet plus AgentSLA's records) and the status vocabulary (active/settled/reclaimed), which tells the agent what states to expect. Missing: behavior when the job id does not exist, and freshness/caching of the off-chain records.

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?

Two sentences, purpose front-loaded, followed by the return-field inventory and the usage cue. The field list is dense but each item informs the agent about what it will receive; no filler words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the return-value burden and does so thoroughly via the field enumeration and status vocabulary. With a single fully documented parameter and annotations covering the safety profile, nothing essential is absent.

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 the only parameter's meaning (job id returned by register_escrow_terms) is already in the schema. The description adds no format, range, or edge-case guidance beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (reads) and resource (one escrow job), with an explicit enumeration of the returned fields (status, creator, provider, listing, endpoint, price, fee, latency limit, created time, reclaim window). This clearly separates it from siblings like register_escrow_terms and get_usdc_escrow_contract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the lifecycle position explicitly: 'Use it after register_escrow_terms to follow a job to completion.' That gives an agent a clear trigger. It does not, however, say when not to use it (e.g., vs. a listing-lookup tool) or what to do if the job is unknown.

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