Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_source_finish

Idempotent

Finish the upload and probe its duration in the background. Poll source_get until ready.

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_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes
upload_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the duration probe runs asynchronously in the background and requires polling until ready, which an agent could not infer from the structured fields.

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 sentences, zero waste, with the key action front-loaded and the follow-up polling instruction second. Nothing redundant.

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?

Covers the async lifecycle and the polling step, which is the essential missing piece for a background operation. However, with no output schema and no parameter prose, it leaves unclear what the probe result looks like and how the two required identifiers should be obtained.

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% — both required parameters (source_id, upload_key) appear only as typed patterns with no prose. The description never mentions either parameter, so it does not compensate for the coverage gap or explain where upload_key originates.

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 and resource: finishing a source upload plus a background duration probe. It clearly differs from siblings like switchboard_source_append and switchboard_source_cancel by describing the finalization step, though it does not name 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 Guidelines3/5

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

Provides a follow-up instruction — poll switchboard_source_get until ready — which tells the agent what to do after finishing. It does not state prerequisites (e.g., that an upload_key must come from an open/append step) or when to prefer this over cancel.

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