Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_source_open

Prepare a bounded media upload. Preserve the returned source_id and upload_key.

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": {
      "filename": "<filename>",
      "total_bytes": "<total_bytes>"
    },
    "name": "switchboard_source_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
upload_keyNo
total_bytesYes

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 already state readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that the call returns source_id and upload_key and that these must be retained, which is genuinely useful given there is no output schema, but it omits size limits, key expiry, and whether the source must later be finished or cancelled. For a non-idempotent state-creating call, that is a substantial behavioral gap.

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

Conciseness4/5

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

Two short sentences with no filler, and the key retention instruction is front-loaded after the purpose statement. The brevity is efficient rather than bloated, though it verges on under-specification for a three-parameter stateful tool.

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?

With no output schema, no enum hints, and 0% schema description coverage, this short description leaves too much unresolved: parameter meanings, the upload lifecycle, and how the returned identifiers are consumed downstream. An agent would need to open sibling definitions to use this correctly.

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%, so the description must carry the burden, and it does not: filename and total_bytes are never explained, and total_bytes' exclusiveMinimum/maximum bounds go unmentioned. The word 'bounded' hints at a byte cap but the description never connects it to total_bytes. Worse, upload_key appears in the schema as an input property yet the description frames it as a returned value, leaving the parameter's role ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Prepare' plus 'bounded media upload' signals an upload-initialization step, which is more than a restatement of the name, but 'source' is never defined and nothing distinguishes this from switchboard_source_append, switchboard_source_finish, or switchboard_source_cancel. An agent can guess it starts an upload but cannot confidently place it in the workflow.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to the obvious siblings that complete or abandon the upload. The only imperative is 'Preserve the returned source_id and upload_key', which is a post-call instruction rather than usage guidance.

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