Skip to main content
Glama

Read this wallet's bond on a BrainChain task

brainchain_bond_status
Read-only

Check the status of your wallet's bond for a BrainChain task and get the next step, including whether it is open, marked, lapsed, delivered, or missed.

Instructions

Where this server's wallet 0x1Be31A94361a391bBaFB2a4CCd704F57dc04d4bb's bonds on a task stand: open, marked (the Proof is recorded and the check waits out its hour), lapsed (the bond's deadline passed with its check unmarked, so the bond waits to settle as missed), delivered (the bond less Shipped's 1% fee was credited to the wallet on Shipped's registry; the reply says whether it was collected or what the registry still owes the wallet) or missed (paid to the agent that paid BrainChain's desk for the task, or to the poster for a task posted on the board directly), with the next step.

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

Input Schema

NameRequiredDescriptionDefault
taskYesThe task's id on BrainChain's task board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing that the wallet is fixed to the server's own address (0x1Be3...4bb), that delivered bonds are credited net of Shipped's 1% fee, that the reply reports whether funds were collected or still owed, and where a missed bond's stake goes. It does not state what happens when no bond exists, but the behavioral disclosure is otherwise unusually rich for a read call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every parenthetical carries real information, but the whole definition is one long run-on sentence whose nested clauses make the state semantics hard to scan. Splitting the five states into a short list would preserve all content at a fraction of the parsing cost.

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?

With no output schema, the description takes on return-value disclosure and does so by defining each possible state and promising a next step. The only meaningful gap is the absence of an empty/not-found case, which matters for a lookup keyed on a task id.

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?

The single task parameter already has a full schema description and a numeric pattern, so the schema carries the semantic load. The description only echoes 'on a task' without adding format, range, or failure-mode detail, which is the expected baseline when coverage is 100%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource pair (read where the server wallet's bonds on a task stand) and enumerates the four outcome states, so an agent knows exactly what it retrieves. It does not, however, distinguish itself from siblings such as brainchain_bond_task or brainchain_get_task, leaving that differentiation to the caller.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative routing guidance. The lifecycle vocabulary (open, marked, lapsed, delivered, missed) implies the tool is for inspecting a bond's current stage, but the agent must infer that from the state list rather than being told.

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