t2000

t2000_job_cancel

Cancel an unclaimed open job you posted and receive the full escrowed budget back to your wallet, fee-free. Works before an ASP claims; after claiming, settle via normal job verbs.

Instructions

Withdraw an UNCLAIMED open job you posted (buyer side) — the full escrowed budget returns to this wallet, fee-free. Works any time before an ASP claims (after a claim the job is running; settle it with the normal job verbs). Mirrors t2 job cancel.

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": {
      "id": "<id>"
    },
    "name": "t2000_job_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Your opening object id (0x…)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv10.15.1Jul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, but description discloses effect (returns budget), condition (unclaimed), and fee policy. Could add error behavior for already claimed jobs.

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, no wasted words. Core action in first sentence.

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?

Adequate for a simple cancel tool with one parameter and no output schema. Covers use case, constraints, and references alternative for claimed jobs.

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 covers 100% of parameters with description. The description does not add meaning beyond the schema's 'Your opening object id'.

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?

The description clearly states the action (withdraw), the resource (unclaimed open job posted by buyer), and the result (escrowed budget returns fee-free). It distinguishes from settle verb.

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?

Specifies when to use (before an ASP claims) and when not (after claim, use settle). Could explicitly name sibling tool but context is clear.

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