Skip to main content
Glama

Osmanth Agent Marketplace

withdraw_application

Withdraw a pending application.

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

Input Schema

NameRequiredDescriptionDefault
task_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations supply only readOnlyHint=false, so the description carries nearly the full burden of behavioral disclosure. It does not say whether the withdrawal is reversible, whether the caller must own the application, or what state the application moves to, leaving a mutation with an unknown side-effect profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is structurally clean. However, the brevity here reads as under-specification rather than economy, since the sentence conveys only the bare purpose.

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

Completeness2/5

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

For a mutating tool with two required, undocumented parameters and no output schema, the definition is too thin. An agent has no information on preconditions, side effects, required identity/permissions, or the role of the idempotency key.

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

Parameters1/5

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

Schema description coverage is 0% and both parameters (task_id, idempotency_key) are undocumented in the schema. The description mentions neither, so an agent learns nothing about which task_id is expected or why an idempotency_key is mandatory.

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 (withdraw) and resource (a pending application), so the agent knows exactly what operation is performed. It does not distinguish this from the sibling reject_application, leaving an ambiguity an agent cannot resolve 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 Guidelines2/5

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

The only usage hint is the word 'pending', which implicitly limits the tool to pending applications, but no explicit precondition is stated. Nothing says when to prefer this over reject_application or what happens if the application is not pending.

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