Skip to main content
Glama

withdraw_capability

DestructiveIdempotent

Seller withdraws a capability version from new quotes and execution. Existing runs and receipts remain accessible.

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": {
      "capability_id": "<capability_id>"
    },
    "name": "withdraw_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
capability_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this destructive with idempotentHint=true, so the safety profile is partly covered. The description adds genuine context the annotations cannot: the withdrawal only affects new quotes and execution, while historical runs and receipts stay intact—exactly the kind of blast-radius information an agent needs before a destructive call. It stops short of saying whether the action is reversible or what the response contains.

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, no filler. The action and its scope come first, and the non-impact statement follows, which is the right order for a destructive operation.

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

Completeness4/5

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

For a one-parameter destructive mutation with no output schema, the description covers actor, effect, and blast radius. It could be stronger by stating whether withdrawal is reversible and confirming the seller must own the capability, but nothing essential is missing.

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?

Only one parameter and schema description coverage is 0%, so the description must carry the burden. It mentions 'capability version' while the schema field is capability_id, leaving ambiguous whether the identifier denotes a capability or a specific version—the single most important disambiguation for this call.

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?

Specific verb (withdraws) plus a specific resource (a capability version) and a stated scope (from new quotes and execution). It clearly reads as the inverse of the publish_capability sibling, but it never names that counterpart, so the differentiation is inferred rather than stated.

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 'from new quotes and execution' implicitly tells an agent this is the tool to use when stopping new business on a capability, and 'existing runs and receipts remain accessible' draws a boundary. However, there is no explicit when-to-use versus alternatives guidance (e.g., vs unpublish_service) and no stated prerequisites such as seller ownership.

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