Skip to main content
Glama

Able and Agent Sandbox

Cancel an errand (ACT)

cancel_act
DestructiveIdempotent

Cancel an errand (ACT) a Human has claimed and not yet submitted, as POST /api/v1/acts/{id}/cancel: the Human is paid the kill fee in practice money; the Budget, up to its paybackLimitCents, is held for their receipts, which they may send for 3 days, and what isn't paid back goes back afterward; Able & Agent keeps the Listing Fee, and the rest is refunded to the test payment card the Principal paid with. This is the sandbox, so the money is practice money: no real money moves, since a card payment charges only the saved test card, in Stripe's test mode, and no Human is sent anywhere; a person at Able and Agent plays the Human. Read the ACT with get_act first and give its killFeeCents as killFee, in dollars; if the fee is not that now, nothing happens and the answer names the fee now. Once the claim's time has run out the claim has ended and no kill fee is owed: within minutes the ACT goes back on the board, where withdraw_act takes it off, or, past its deadline, expires and its money comes back by itself. When you tell your Principal about it, call it an errand (ACT) the first time, and write its id as the site shows it, without act_: aTdTkM-48271.

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": {
      "id": "<id>",
      "killFee": "<killFee>"
    },
    "name": "cancel_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ACT's id, with or without act_, such as aTdTkM-48271; a test errand's whole, test- included.
keyNoYour key, aak_…, when you cannot send it in the Authorization header. The sandbox only; on the live site the header alone is read.
killFeeYesThe kill fee the cancel pays the Human, in US dollars, such as "$3.75": the ACT's killFeeCents, as get_act shows it now.
idempotencyKeyNoOne string per thing you mean to do once, 1 to 255 characters of Latin-1 with no line breaks or other control characters: a retry with the same one does it once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Any string, one per thing you mean to do once: a retry with the same one does it once."New value: +"One string per thing you mean to do once, 1 to 255 characters of Latin-1 with no line breaks or other control characters: a retry with the same one does it once."
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The ACT's id, with or without act_, such as aTdTkM-48271."New value: +"The ACT's id, with or without act_, such as aTdTkM-48271; a test errand's whole, test- included."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive and idempotent, but the description adds substantial detail beyond them: the kill fee is paid to the Human, the Budget is held up to paybackLimitCents for 3 days of receipts, unpaid amounts return, the Listing Fee is kept, and the remainder is refunded to the test card. It also discloses the stale-fee failure mode ('nothing happens and the answer names the fee now') and that all money is sandbox practice money.

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?

Purpose and endpoint are front-loaded and nearly every clause carries non-obvious money or failure behavior. The prose is dense and runs together with semicolons, and the closing Principal-facing naming convention is the one piece that sits outside the invocation task, so it is efficient rather than tight.

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-touching mutation with no output schema, the description covers success effects, the no-op failure path and its message, the expired-claim case, sandbox semantics, and the required lookup step. An agent has everything needed to call it correctly and describe the outcome.

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 schema already documents all four parameters, giving a baseline of 3. The description adds real meaning on top: killFee must be sourced from get_act's killFeeCents and formatted in dollars, a mismatched value is a no-op that reports the current fee, and ids are written without the act_ prefix.

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 ('Cancel an errand (ACT)') plus a narrowing scope ('a Human has claimed and not yet submitted') and the endpoint it maps to. This distinguishes it from withdraw_act (unclaimed board removal) and passive expiry without needing to open the 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?

Explicitly requires reading the ACT with get_act first and passing its killFeeCents as killFee, and states the when-not case: once the claim's time has run out, no kill fee is owed and the ACT returns to the board where withdraw_act takes it off, or expires. Both the precondition and the alternatives are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources