Comunio MCP

Withdraw a bid

withdraw_bid

Cancel an outgoing bid you placed on a player, removing it from the market. Use the offer ID from get_offers; only outgoing offers are eligible.

Instructions

Withdraw a bid the manager has placed, so it is no longer in the running.

This changes what the manager has committed to. Confirm which bid with the user before calling it. Ids come from get_offers; only offers whose direction is outgoing can be withdrawn.

Refuses outright if the id belongs to an offer for one of the manager's players rather than a bid they made. Comunio uses the same request for both, so telling them apart is done here rather than left to chance.

A withdrawn bid cannot be restored, but a new one can be placed while the market is still open.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`offer_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether Comunio accepted the withdrawal
`price`	No	What the withdrawn bid offered
`player`	No	Who the withdrawn bid was for
`offer_id`	Yes	The offer that was withdrawn

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 9, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations only say readOnly=false, idempotent=false, destructive=false, but the description adds critical behavioral details: it changes what the manager has committed to, is irreversible, and refuses certain inputs. The note that Comunio uses the same request for both directions and the tool disambiguates is valuable beyond structured fields.

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?

The description is well-structured: a clear opening sentence, followed by bolded importance, then prerequisites, edge-case handling, and consequences. Every sentence adds value with no fluff, and the key constraints are front-loaded.

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?

Given there is an output schema (not shown but indicated), the description needn't explain return values. It covers prerequisites, valid inputs, refusal behavior, irreversibility, and the ability to re-place a bid. For a single-parameter tool, this is complete and actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden. It fully explains offer_id: where to get it (get_offers), what values are valid (direction=outgoing), and what it represents (a bid made by the manager, not an incoming offer). This adds complete meaning to the single parameter.

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 clearly states the action ('Withdraw a bid'), the resource ('a bid the manager has placed'), and the outcome ('no longer in the running'). It differentiates from siblings like place_bid and change_bid by specifying it's for outgoing bids only, and explicitly contrasts with incoming offers for the manager's players.

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?

Provides explicit when-to-use guidance: IDs come from get_offers, only offers with direction='outgoing' qualify, and the user should confirm which bid before calling. It also states a clear exclusion (refuses offers for the manager's players) and notes a withdrawn bid cannot be restored but a new one can be placed, giving the agent full decision context.

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