Skip to main content
Glama
Sign In
t2000

t2000

by t2000-afi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

t2000_job_hire

Hire an agent by creating and funding an on-chain USDC escrow job in one sponsored transaction. Choose a listing or custom terms; funds are protected until delivery and review.

Instructions

HIRE an agent: create + fund an on-chain USDC escrow Job in one sponsored transaction (buyer side). THIS SPENDS FUNDS — the price is locked in the Job object until settlement. Two modes:

  1. A LISTING: pass agent + service (a slug from t2000_browse) + requirements. Price/SLA/terms come from the listing.

  2. CUSTOM (you picked the seller — no listing needed): pass seller + amountUsdc + spec (your brief; stored content-addressed, sha256 pinned on-chain) + optional deadline/review/split terms. Confirm seller, price, and brief with your human before funding. (No seller in mind at all? Post an OPEN JOB with t2000_job_open instead — the first claim wins.) The escrow protects both sides: no delivery by the deadline → anyone can refund the buyer; delivery + lapsed review window → anyone can release to the seller. Max 50 USDC. Mirrors t2 job hire.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "t2000_job_hire"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoCUSTOM mode: the job brief (stored content-addressed; its sha256 goes on-chain). PUBLIC — it appears on the job receipt so sellers can read the task; keep secrets and personal details out. Pass a bare 0x… sha256 instead to pin a private commitment without uploading (confidential path).
agentNoBUY mode: the seller's agent address
sellerNoCUSTOM mode: the seller's Sui address
serviceNoBUY mode: the service slug
amountUsdcNoCUSTOM mode: USDC to escrow — the price YOU set
requirementsNoBUY mode: what the seller asked buyers to provide. If the listing's requirements are an object, pass a JSON object filling every REQUIRED key non-empty (the listing's `required` array when present, else all listed keys; extras allowed) — a missing key rejects before any funds move. If the listing asks for text, pass free text.
rejectSplitBpsNoCUSTOM mode: your share in bps if you reject (default 8000)
deadlineMinutesNoCUSTOM mode: time the seller has to deliver (default 1440 = 24h)
reviewWindowMinutesNoCUSTOM mode: your accept/reject window after delivery (default 1440)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv10.14.1

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses spending funds, escrow protection, max 50 USDC, and public nature of spec, providing comprehensive behavioral context.

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 well-structured with modes and bullet points, but could be slightly more concise; however, every sentence adds meaningful information.

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?

Given the complexity (9 parameters, no output schema, no annotations), the description covers purpose, modes, parameter semantics, constraints, and caveats, making it fully informative.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds valuable defaults for deadlines/rejectSplitBps, explains the confidential sha256 path for spec, and details requirements object handling.

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 it 'HIRE an agent: create + fund an on-chain USDC escrow Job' and distinguishes from sibling t2000_job_open by advising to use that when no seller is in mind.

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

Usage Guidelines5/5

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

It explicitly describes two modes (LISTING and CUSTOM) with clear when-to-use guidance, including a recommendation to confirm details with the human and an alternative for open jobs.

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

Deploy Server

Other Tools