t2000

t2000_job_settle

Settle an escrow job by moving funds per outcome: release to seller, reject to split per terms, or refund buyer if no delivery.

Instructions

Settle an escrow job — MOVES THE ESCROWED FUNDS:

release: accept the delivery → funds to the seller (buyer; or ANYONE once the review window lapses — the anti-ghosting crank)
reject: within the review window → funds split per the terms agreed at create (buyer only)
refund: no delivery by the deadline → funds back to the buyer (anyone may crank) Check t2000_jobs first — it tells you which of these THIS wallet can run right now. Sponsored (no gas). Mirrors t2 job release|reject|refund.

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>",
      "action": "<action>"
    },
    "name": "t2000_job_settle"
  }
}

Input Schema

Name	Required	Description	Default
`jobId`	Yes	The Job object id (0x…)
`action`	Yes	Which settlement to run

Schema Changelog

Changes observed during successful MCP inspections.

Addedv10.13.4Jul 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It explains the effects of each action (e.g., 'release: accept the delivery → funds to the seller'), mentions sponsorship ('Sponsored (no gas)'), and notes that actions can be executed by different roles. Lacks info on error states or idempotency, but is forthcoming about core behavior.

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?

Description is four concise sentences, front-loaded with purpose, then action details, then usage hint. Every sentence adds value with no redundancy.

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

Completeness3/5

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

No output schema is provided, and the description does not explain what the tool returns (e.g., transaction hash, success status). For a tool that performs a blockchain settlement, this is a notable gap. The description otherwise covers inputs and behavior well.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with adequate descriptions for 'jobId' and 'action'. The description adds crucial context to the 'action' enum by explaining the business logic of each value (e.g., 'release' sends funds to seller). This goes beyond the schema's simple 'Which settlement to run'.

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?

Description clearly states 'Settle an escrow job — MOVES THE ESCROWED FUNDS' and enumerates three specific actions (release, reject, refund) with distinct outcomes. It differentiates from sibling tools like t2000_job_create and t2000_job_review by focusing on settlement.

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?

Provides explicit guidance: 'Check t2000_jobs first — it tells you which of these THIS wallet can run right now.' This tells the agent when to use the tool and what precondition to verify. Could be stronger by explicitly naming alternatives, but the instruction is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.