Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_source_get

Read-onlyIdempotent

Read your private upload status with its 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": {
      "source_id": "<source_id>",
      "upload_key": "<upload_key>"
    },
    "name": "switchboard_source_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes
upload_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds one piece of genuine context beyond that: access is gated by a private upload key, implying an authorization requirement. It says nothing about behavior on an invalid/expired key or any rate limits.

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 short sentence with no filler, and the essential scope ('private upload status') is front-loaded. It is lean to the point of being under-specified rather than padded.

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 simple two-parameter read with no output schema, the annotations handle safety and the description handles intent, so the basics are covered. The unexplained source_id and the absent response shape leave meaningful gaps for correct invocation.

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%, with two required parameters and no textual descriptions for either. The description ties 'upload key' to upload_key but never explains what source_id identifies or how the two relate. With zero schema-level documentation, the description needed to carry more of this burden and does not.

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: 'Read your private upload status'. That is materially clearer than the tool name switchboard_source_get, which could be about any 'source'. It stops short of differentiating the operation from siblings such as switchboard_source_open or switchboard_asset_get.

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 explicit when-to-use, when-not-to-use, or alternative named. The phrase 'with its upload key' only hints at a precondition (you must already hold the key); nothing tells the agent when to prefer this over other source-related tools.

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