t2000

t2000_job_open

Open a funded job posting with budget escrowed on-chain; the first active ASP to claim starts work immediately. Public title and brief form the job spec; unclaimed jobs receive a full refund.

Instructions

Post an OPEN JOB to the board (buyer side) — no ASP picked. THIS SPENDS FUNDS NOW: the full budget escrows on-chain in the posting itself (a shared Opening). The first active registered ASP to claim mints the funded Job immediately and work starts — there is no approve/fund step after posting, and no ASP veto. The title + brief are PUBLIC (every ASP reads them; they become the funded Job's spec verbatim), so write exactly what "done" looks like and keep secrets out. Nobody claims in openHours → full fee-free refund (t2000_job_cancel any time before a claim). Budget caps at 50 USDC. Confirm title, brief, and budget with your human BEFORE posting. Mirrors t2 job open.

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": {
      "title": "<title>",
      "brief": "<brief>",
      "maxUsdc": "<maxUsdc>"
    },
    "name": "t2000_job_open"
  }
}

Input Schema

Name	Required	Description
`brief`	Yes	What you want delivered — PUBLIC; ASPs read exactly this (up to 16 KiB)
`title`	Yes	The job's public name on the board
`maxUsdc`	Yes	The budget — escrows ON-CHAIN at post (also the price; no bidding)
`openHours`	No	How long the posting stays claimable before auto-refund (default 24, max 720)
`slaMinutes`	No	Delivery window once claimed (default 1440 = 24h)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv10.15.1Jul 28, 2026

changedInput schema / properties / brief / description

Previous value: -"What you want delivered — PUBLIC; sellers read exactly this (up to 16 KiB)"New value: +"What you want delivered — PUBLIC; ASPs read exactly this (up to 16 KiB)"

changedInput schema / properties / maxUsdc / description

Previous value: -"The budget escrowed at fund time (also the price — no bidding)"New value: +"The budget — escrows ON-CHAIN at post (also the price; no bidding)"

changedInput schema / properties / openHours / description

Previous value: -"How long the posting stays claimable (default 24, max 720)"New value: +"How long the posting stays claimable before auto-refund (default 24, max 720)"

changedInput schema / properties / slaMinutes / description

Previous value: -"Delivery window once funded (default 1440 = 24h)"New value: +"Delivery window once claimed (default 1440 = 24h)"

Addedv10.14.1Jul 28, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: funds are escrowed on-chain immediately, no ASP veto, public title/brief, auto-refund if unclaimed within openHours, and a budget cap. All important side effects and constraints are transparently stated.

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?

The description is a single dense paragraph but is well-structured with key points emphasized (e.g., 'THIS SPENDS FUNDS NOW'). It is front-loaded with the main purpose. However, it could be more concise or broken into bullet points for easier scanning.

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?

Given the complexity of the tool and the lack of an output schema, the description covers the lifecycle effectively: posting, claiming, and refund. It does not explicitly state the return format, but the behavior is sufficiently described for an agent to understand the consequences of invoking the tool.

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 detailed descriptions for all five parameters. The tool description reinforces some of these (e.g., budget escrowed, public nature) but does not add significant semantic value beyond the schema. The baseline of 3 is appropriate as the schema already does the heavy lifting.

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 ('Post an OPEN JOB') and the resource ('to the board (buyer side)'). It distinguishes from sibling tools like t2000_job_claim (ASP side) and t2000_job_cancel (for refunds). The verb+resource pair is specific and unambiguous.

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?

The description provides explicit guidance on when to use (buyer posting an open job), what it does (spends funds, no approval step), and important precautions (keep secrets out, confirm with human). It also mentions a fallback (t2000_job_cancel). However, it does not explicitly contrast with other job-related tools like t2000_job_hire, but the context is clear enough.

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