Skip to main content
Glama

Withdraw

withdraw
DestructiveIdempotent

Withdraws the application. Documents and personal details are deleted at once.

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": {
      "school": "<school>",
      "application_id": "<application_id>",
      "application_token": "<application_token>"
    },
    "name": "withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolYesThe school's slug from list_schools, e.g. "vvs"
application_idYes
application_tokenYesThe application_token returned by verify_email for this school

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower. The description does add genuinely new information beyond annotations — that documents and personal details are deleted and that deletion happens immediately — but it omits whether the application_token is invalidated, whether deletion is reversible or recoverable, and what the caller receives in response.

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 short sentences, front-loaded with the action and followed immediately by the consequence. No filler, no restatement of the name or title.

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?

For a destructive, irreversible-looking operation with no output schema, the description covers the most important fact (what gets deleted and how fast) but leaves post-conditions unspecified: state of the token afterward, behavior when the application is already withdrawn, and whether any data survives. Given the 3 required parameters and the destructive annotation, this is adequate but thin.

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?

The description says nothing about the three required parameters, adding zero meaning beyond the schema. With only 67% schema description coverage and application_id documented solely by format/pattern, the description should have compensated but does not explain that application_token must come from verify_email for the same school or that school is the slug from list_schools.

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?

The description names a specific verb and resource ("Withdraws the application"), which is unambiguous and clearly distinct from submit_application or update_application by implication. It stops short of explicitly naming a sibling or stating the scope of the withdrawal.

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?

The phrase "deleted at once" implies this is a terminal, one-way action, which implicitly signals it should be used instead of update_application when the user wants to cancel. There is no explicit when-to-use or when-not-to-use guidance, and no mention of whether a confirmation step or alternative (e.g., editing) should be preferred.

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.