Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_source_append

Idempotent

Append one bounded base64 media chunk at the exact offset; repeat the same chunk to recover.

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>",
      "offset": "<offset>",
      "data_b64": "<data_b64>",
      "sha256": "<sha256>"
    },
    "name": "switchboard_source_append"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetYes
sha256Yes
data_b64Yes
source_idYes
upload_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint and destructiveHint=false, so the description's real contribution is the retry contract — resend the identical chunk rather than a new one — which is not derivable from the annotations. It still omits what happens on checksum mismatch, offset collision, or chunk size violations, and does not mention auth requirements.

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?

A single front-loaded sentence with the offset constraint before the recovery hint; no filler. It is nearly too terse for the amount of contract it needs to convey, but no wording is wasted.

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?

This is a mutating, open-world, five-required-parameter upload step with no output schema and no parameter documentation. The description covers chunking and retry but leaves the upload session model, sequencing relative to open/finish, checksum semantics, and failure behavior unexplained.

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% across five required parameters, so the description carries the full burden and largely fails. It clarifies only offset and data_b64 (base64, bounded); source_id, upload_key, and especially sha256 (presumably a chunk or content digest, but never stated) get no meaning beyond their regex patterns.

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?

The description uses a specific verb ('Append') plus resource ('bounded base64 media chunk') and pins semantics to 'the exact offset'. It does not name or contrast any sibling (e.g. switchboard_source_open, switchboard_source_finish, switchboard_chunk), so an agent must infer where this sits in the upload sequence.

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?

Usage is only implied: 'repeat the same chunk to recover' tells the agent how to handle a failed append, and 'at the exact offset' implies ordered sequential appends. It never states the prerequisite (source must be opened first) or when to call switchboard_source_finish instead of appending more.

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