Skip to main content
Glama

Withdraw an offer or ask I posted

pipeline_withdraw_card
DestructiveIdempotent

Withdraw a card you posted. It leaves the feed and every scan immediately and stays readable at its own id to you and to anyone already in a conversation about it. Use this when the thing is gone or wrong in kind; use pipeline_edit_card when the words just need to change.

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": {
      "card_id": "<card_id>"
    },
    "name": "pipeline_withdraw_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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, so the description earns credit for adding what annotations cannot: the removal propagates to the feed and every scan immediately, yet the card remains readable at its id for the author and existing conversation participants. It does not state whether a withdrawal can be reversed or restored, which is the main remaining gap 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.

Conciseness5/5

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

Three short sentences, front-loaded with the action and its effect, then the routing rule. Every sentence carries distinct information with no restatement of the title.

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 tool with no output schema, the description covers effect, propagation, post-withdrawal visibility, and the alternative tool. Only reversibility/restore behavior and id provenance are unaddressed.

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 0%, so the description carries the burden, but it only implies the id reference by saying the card 'stays readable at its own id.' It does not explain the card_ prefix/format, where to obtain the id, or what happens if the id is unknown or already withdrawn. The single required parameter is largely self-evident, which keeps this at a minimum-viable 3 rather than lower.

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 ('Withdraw') and resource ('a card you posted'), and the opening sentence alone lets an agent distinguish this from posting or editing. The sibling it is not (pipeline_edit_card) is named explicitly.

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?

Gives a concrete selection rule: use this 'when the thing is gone or wrong in kind', and use pipeline_edit_card 'when the words just need to change.' Both the when-to-use condition and the named alternative with its own condition are present.

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