Skip to main content
Glama

Withdraw a question to my human

withdraw_ask
DestructiveIdempotent

Withdraw a question to your owner that is still waiting for an answer, because you no longer need it. Its answer links then tell your owner you withdrew it, and record nothing. It counts as done (status withdrawn) but keeps its place in your ask limits until its expires_at, so withdrawing never lets you ask more. Withdrawing again changes nothing; an answered question cannot be withdrawn (409 ask_answered). To remove a done question with its answer, delete_ask.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ask_id": "qst_exampleexampleexample2",
      "instance_id": "ask_exampleexampleexample2"
    },
    "name": "withdraw_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
ask_idYesask_id (qst_...) from ask_human.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ask_id / description
      Previous value: -"ask_id from ask_human."New value: +"ask_id (qst_...) from ask_human."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "ask_id": "qst_exampleexampleexample2",
      +    "instance_id": "ask_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description adds substantive context beyond them: the answer links record nothing, the ask goes to status 'withdrawn' and keeps counting against ask limits until expires_at so withdrawing never frees quota, and repeat withdrawal is a no-op. That is exactly the non-obvious behavioral detail an agent needs before a destructive call.

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?

Front-loaded with the core action and motive, then the consequences, then the error case and alternative. Dense but nearly every clause carries information; small cost for wording like 'Its answer links then tell your owner you withdrew it' which reads awkwardly.

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 3-parameter destructive mutation with no output schema, the description covers outcome (status withdrawn, nothing recorded), side effects (quota retained until expires_at), idempotency, and the failure mode. 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 description coverage is 100%, with ask_id and instance_id both documented in-schema and passport_token explained as a fallback auth path. The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb (withdraw) and resource (a pending question to the owner) and states the motive condition ('because you no longer need it'). It also explicitly distinguishes itself from delete_ask, which handles done questions with answers, so an agent can route correctly from the description alone.

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 clear when-to-use case (question still awaiting an answer and no longer needed), an explicit when-not case (an answered question cannot be withdrawn, returns 409 ask_answered), and names the alternative tool (delete_ask) for the adjacent scenario. Idempotent re-invocation is also addressed.

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.