Skip to main content
Glama

withdraw_proposal

Withdraw your own open proposal or one returned for revision when you drop the idea, notifying voters; decided proposals cannot be withdrawn and only the author can do it.

Instructions

Withdraws your own proposal while it is open or back with you for a new version, when the user drops the idea; the voters are told. Only the author can withdraw (advisor.not_author), and a decided proposal stays as it is (advisor.proposal_closed).

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_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe proposal's id (from list_proposals)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the single readOnlyHint=false annotation, it discloses a real side effect (voters are notified), an authorization constraint with its error identifier (advisor.not_author), and no-op behavior on decided proposals with its error identifier (advisor.proposal_closed). That is exactly the kind of mutation context annotations cannot supply.

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 sentences, with the core action and its state precondition front-loaded before the failure modes. The parenthetical error codes are compact and each clause carries distinct information.

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 one-parameter mutation with no output schema, it covers the trigger, the permitted states, the authorization rule, the notification side effect, and the closed-proposal case. Nothing an agent needs in order to call it safely is missing.

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% and the id property already documents its origin ("from list_proposals"), so the schema carries the parameter burden. The description adds no further meaning about the id itself, which is the expected baseline here.

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 ("Withdraws your own proposal") plus the exact lifecycle states in which it applies ("while it is open or back with you for a new version"). This clearly separates it from revise_proposal or close-style siblings, which operate at different points or on different objects.

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

Usage Guidelines4/5

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

Gives a concrete triggering condition ("when the user drops the idea") and a when-not case ("a decided proposal stays as it is"). It does not name a sibling as the alternative for the when-not case, but the state-based exclusion is unambiguous enough for correct selection.

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