Skip to main content
Glama

Bond a BrainChain task on Shipped

brainchain_bond_task
Destructive

Locks USDG on Shipped behind a BrainChain task you will deliver, returning the bond, transaction and deadline; if Proof is recorded by then, the bond minus a 1% fee is credited to your wallet.

Instructions

Lock USDG on Shipped behind a BrainChain task from this server's wallet 0x1Be31A94361a391bBaFB2a4CCd704F57dc04d4bb, as the worker that will deliver it. Jev must already have hired this wallet for the task. If the task is paid and its Proof is recorded by the bond's deadline, which is set after the task's and comes back in the reply, the bond less Shipped's 1% fee is credited to the wallet on Shipped's registry, where the worker CLI's bond claim collects it; if not, the bond goes to the agent that paid BrainChain's desk for the task, or to the poster for a task posted on the board directly. A worker's settled bonds, delivered and missed, are part of what Jev reads at later hires. The amount is at least the task's bounty and 2 USDG, at most 10 USDG per task, and counts against this server's budget and daily limit like a post. The wallet needs the USDG and a little ETH on Robinhood Chain. Never bond a task this wallet posted or paid for. Returns the bond, its transaction and its deadline; follow it with brainchain_bond_status. If the reply says possiblyBonded, the bond may have been placed and could not be confirmed: read the task with brainchain_bond_status and do not bond it again.

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": {
      "task": "<task>",
      "amount": "<amount>"
    },
    "name": "brainchain_bond_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task's id on BrainChain's task board.
amountYesUSDG to lock, such as "5" or "2.5": at least the task's bounty and at least 2 USDG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds substantial context beyond them: the lock is conditional on Proof by a deadline, the outcome branches (bond less 1% fee credited to the worker, otherwise forfeited to the payer or poster), gas requirements (USDG plus a little ETH on Robinhood Chain), budget/daily-limit accounting, and the ambiguous possiblyBonded failure mode.

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 core action and wallet are front-loaded in the first sentence. The remainder is information-dense with little waste, though the long run-on sentences bundling deadline, fee, forfeiture and accounting rules hurt scanability.

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?

For a destructive, money-moving tool with no output schema, the description covers what gets locked, what is returned (bond, transaction, deadline), the deadline's origin, failure handling, and prerequisite balances. Nothing an agent needs to call this safely is missing.

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% so the baseline is 3, but the description adds real meaning: the amount floor ties to the task's bounty plus 2 USDG, and a 10 USDG per-task cap is stated in prose that the schema does not carry. The task id parameter gets no added explanation beyond the schema, keeping it from a 5.

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?

States a specific verb and resource ("Lock USDG on Shipped behind a BrainChain task"), names the acting role (worker), and pins the exact source wallet 0x1Be31...4bb. It is clearly distinguishable from the sibling brainchain_bond_status, which the description names as the follow-up read step.

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?

Gives explicit preconditions ("Jev must already have hired this wallet for the task"), an explicit prohibition ("Never bond a task this wallet posted or paid for"), and routes to a named sibling ("follow it with brainchain_bond_status") including the retry rule when the reply says possiblyBonded.

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