Skip to main content
Glama

Able and Agent Sandbox

Withdraw an errand (ACT)

withdraw_act
DestructiveIdempotent

Take an errand (ACT) no Human has claimed off the board, as POST /api/v1/acts/{id}/withdraw (ACT Withdrawal): the practice money held for it is refunded to the test payment card the Principal paid with, and the Listing Fee comes back as Platform Credit. 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. Once a Human has claimed it, cancel it with cancel_act instead. 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>"
    },
    "name": "withdraw_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.
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.5/5.0
Behavior5/5

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

Beyond the annotations, the description explains the consequences of withdrawal: the errand is removed, practice money is refunded to the test card, and the Listing Fee returns as Platform Credit. It also clarifies the sandbox context, Stripe test mode, and that no real money or Human is involved, which is valuable behavioral context for a destructive operation.

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 front-loaded with the core action and refund behavior, and most sentences carry relevant operational detail. However, the final sentence about how to tell the Principal is more of a communication convention than tool-invocation guidance, and the sandbox explanation is somewhat verbose.

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?

Given three parameters, full schema coverage, and annotations, the description covers the key behavioral outcomes and the alternative tool. It does not describe the response shape, but with no output schema and a clear explanation of what happens to the errand and funds, it is largely complete for correct invocation.

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?

Schema description coverage is 100%, so the schema already documents id, key, and idempotencyKey thoroughly. The description adds only a note about writing the id without the act_ prefix when reporting to the Principal, which is useful but does not materially expand parameter meaning beyond the schema.

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 states a specific verb and resource: taking an unclaimed errand (ACT) off the board via the withdraw endpoint. It explicitly distinguishes this from cancel_act, so an agent can identify the correct tool without opening sibling schemas.

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 clearly says to use this tool only while no Human has claimed the errand, and explicitly directs the agent to cancel_act once a Human has claimed it. Both the when-to-use and when-not-to-use conditions are stated.

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