Skip to main content
Glama
aibtc-mcp-server
by aibtcdev

bounty_cancel

Cancel an open or judging bounty as its poster before any submission is accepted. Supply a reason and ruling URL so the board shows why it closed.

Instructions

Cancel a bounty. Only the poster can call this, and only while status is 'open' or 'judging' (i.e. before any submission has been accepted).

Closing a bounty because no entry met the terms is also a cancel. Pass 'reason' (up to 500 characters) and 'ruling_url' (an https:// link to the published ruling) so the board shows why it closed, rather than looking like the poster walked away. Neither may contain '|'.

Signs with BIP-322 over: "AIBTC Bounty Cancel | {bountyId} | {signedAt}" With reason or ruling_url: "AIBTC Bounty Cancel | {bountyId} | {signedAt} | {reason} | {rulingUrl}" (empty string for the missing one)

Tip: call earning_opportunities to see how to put your assets to work.

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": {
      "bounty_id": "<bounty_id>"
    },
    "name": "bounty_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy the bounty closed, e.g. no entry met the terms
bounty_idYesBounty ID to cancel
ruling_urlNohttps:// link to the published ruling

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.77.4
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Why the bounty closed, e.g. no entry met the terms",
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedInput schema / properties / ruling_url
      Added value: +{
      +  "description": "https:// link to the published ruling",
      +  "maxLength": 500,
      +  "type": "string"
      +}
  2. First observedv1.77.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the authorization requirement (poster only), the state precondition (open/judging), and the exact BIP-322 signing payload, including how the message changes when reason or ruling_url is present. What is missing is post-call behavior — whether the cancel is reversible, what is returned, and whether any funds or escrow are affected.

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 critical constraints are front-loaded in the first two sentences, and the signing format is set off cleanly. The closing 'Tip: call earning_opportunities' sentence is unrelated promotional content that does not help an agent invoke this tool correctly, which keeps it from a 5.

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?

For a three-parameter mutation with no annotations and no output schema, the definition covers authorization, preconditions, field constraints, and signing requirements thoroughly. The remaining gap is the absence of any statement about the result of a successful cancel, which matters since no output schema exists to fill it in.

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 already 100%, so each parameter is documented, but the description adds real meaning beyond it: the 500-character cap, the https:// requirement, the prohibition on '|' in either field, and the fact that a missing field is serialized as an empty string in the signed message. That last detail is only knowable from the description and directly affects whether the call succeeds.

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 first sentence gives a specific verb and resource ('Cancel a bounty') and immediately narrows it with the actor and status preconditions. An agent can distinguish this from bounty_accept, bounty_submit, or bounty_get without opening any schema.

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?

Explicit when-to-use and when-not-to-use: only the poster, and only while status is 'open' or 'judging', i.e. before any submission has been accepted. It also resolves a likely ambiguity by stating that closing a bounty because no entry met the terms is still a cancel, which prevents the agent from looking for a separate close tool.

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