Skip to main content
Glama

withdraw_application

Destructive

Withdraw an open application the signed-in mentee owns. Requires Authorization: Bearer. Only works when list/get_application reports can_withdraw true (sent at least two days ago, no intro session). This cannot be undone.

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": {
      "application_hash": "<application_hash>"
    },
    "name": "withdraw_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_hashYes

Output Schema

NameRequiredDescriptionDefault
hashNoPass to pay_application.
errorNo
statusNodraft, new, pending, accepted, rejected, withdrawn.
unreadNoTrue when the mentee has an unread Pinax message.
messageNo
pay_urlNoREST URL that accepts an MPP credential if credits are short.
payableNoTrue when the mentor accepted and payment is due.
messagesNo
next_stepNo
plan_hashNo
price_usdNo
created_atNo
credits_usdNo
mentor_nameNo
status_noteNo
can_withdrawNoTrue when withdraw_application will succeed.
dashboard_urlNo
action_requiredNoreply_to_mentor, waiting_on_mentor, book_intro_call, or start_mentorship.
mentor_usernameNo
sent_message_idNo
intro_call_scheduledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's "cannot be undone" mostly reinforces existing signal. However, it adds information the annotations do not carry: the Authorization: Bearer requirement and the state precondition (can_withdraw) that must hold before invocation. It stops short of describing what the response contains, but an output schema exists to cover that.

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, each earning its place: what it does and on whose behalf, the auth and state prerequisites, then the irreversibility warning. The critical constraint is front-loaded and there is no filler.

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 single-parameter destructive mutation, the definition covers identity scope, auth requirement, the gate condition, and reversibility, and an output schema handles the return value. Nothing an agent needs in order to decide or call correctly 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?

There is one parameter with 0% schema description coverage, so the description must carry the burden. It implies the application is one the signed-in mentee owns and reachable via get_application/list_applications, which hints at where the hash originates, but it never states the format of application_hash or confirms it is the identifier returned by those calls.

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 ("Withdraw an open application") plus a scope qualifier ("the signed-in mentee owns"), which distinguishes it from read-side siblings like get_application and list_applications. An agent can identify the exact operation without opening the schema.

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 an explicit precondition for use — only when list/get_application reports can_withdraw true — and spells out the concrete criteria behind that flag (sent at least two days ago, no intro session). This is an explicit when-to-use gate naming the sibling tools to consult first, which is exactly what routing guidance should do.

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