Skip to main content
Glama

desk_withdraw

Remove a question from the desk when it no longer needs the person, and state why—for example, it was answered by events or is no longer relevant.

Instructions

Take a question off the desk when it no longer needs the person (answered by events, or no longer relevant), saying why.

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": {
      "item": "<item>",
      "reason": "<reason>"
    },
    "name": "desk_withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
reasonYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a mutation (removing an item) but never says whether the item is deleted or archived, whether the reason is persisted and visible to others, whether the withdrawal is reversible, or what permissions are required.

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?

A single sentence that front-loads the action and appends the condition and the reason requirement; nothing is redundant. The line break mid-parenthetical is cosmetic noise but not a waste of words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the triggering condition is stated. What is missing is behavioral detail proportional to an unannotated mutation with two undocumented parameters: fate of the withdrawn item, reversibility, and parameter formats.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate. 'Saying why' maps loosely to 'reason' and 'a question off the desk' to 'item', but there is no indication of accepted identifier format (ID vs. text) or what a valid reason looks like, leaving the caller to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: taking a question off the desk, with the condition (answered by events or no longer relevant) and the obligation to say why. This distinguishes it reasonably from desk_add and desk_answer, though the object 'question off the desk' is looser than a concrete resource name.

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?

Gives a usable trigger ('when it no longer needs the person') with two concrete cases, but offers no exclusion or routing against desk_answer, which plausibly covers the 'answered by events' case. An agent facing a resolved question has to guess between the two.

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