Skip to main content
Glama

Hummingbird

Withdraw an offer

withdraw_offer
DestructiveIdempotent

Withdraws an offer from the pilot buffer, using its private receipt. Its text and reference are cleared.

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": {
      "receipt": "<receipt>"
    },
    "name": "withdraw_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesThe private one-time receipt returned by make_offer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds useful context that the offer's text and reference are cleared. It does not cover permission requirements, error behavior, or whether withdrawal can be reversed, so it stops short of full transparency.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and scope. Every phrase contributes useful information and there is no redundant wording.

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 one-parameter destructive action with strong annotations and full schema coverage, the description covers purpose, input, and what gets cleared. It lacks only edge-case details such as permissions or error handling, which are minor here.

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 coverage is 100%, so the receipt parameter is fully documented in the schema. The description reinforces that the receipt is private and tied to the offer, but adds little semantic detail beyond what the schema already provides.

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 ('Withdraws') and resource ('an offer') with the scope 'from the pilot buffer'. The receipt requirement and withdrawal action clearly distinguish it from make_offer and offer_status.

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

Usage Guidelines3/5

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

Mentions the precondition of using the private receipt returned by make_offer, but does not explicitly say when to use this versus alternatives or when not to use it. Usage is implied by the name and purpose rather than spelled out.

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.