Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_source_cancel

DestructiveIdempotent

Cancel your prepared upload and remove its source data.

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": {
      "source_id": "<source_id>",
      "upload_key": "<upload_key>"
    },
    "name": "switchboard_source_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes
upload_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the useful detail that source data is removed, not just the upload session, but says nothing about permissions, whether partially appended data is lost, or what happens on a retry.

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?

One short sentence with the action and its side effect front-loaded; no filler or redundant phrasing.

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 two-parameter destructive tool with no output schema, the definition covers the core action and the deletion effect, which the annotations already flag as destructive. It is still thin on prerequisites and on how the two required identifiers relate to the upload, so an agent could call it correctly but not confidently.

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% and the description never mentions source_id or upload_key, leaving the agent to infer that the pair identifies the prepared upload. The regex patterns in the schema convey format but not meaning, so the description fails to compensate for the coverage gap.

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 ('Cancel') and resource ('your prepared upload') and adds the consequence ('remove its source data'). This distinguishes it from siblings like switchboard_source_finish or switchboard_source_append, though it never names those alternatives explicitly.

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 phrase 'your prepared upload' implies a precondition, but there is no guidance on when to cancel versus finishing an upload, whether appended chunks are discarded, or what state the source must be in. No alternatives or exclusions are mentioned.

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