Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_sheet_get

Read-onlyIdempotent

Read a saved terminology/game sheet.

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": {
      "sheet_id": "<sheet_id>"
    },
    "name": "switchboard_sheet_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheet_idYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the word 'saved', implying persistence, but says nothing about error behavior for unknown IDs, whether results are cached, or what a sheet contains — minimal value beyond the annotations.

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

Conciseness3/5

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

A single short sentence with no wasted words, but its brevity comes at the cost of under-specification rather than efficient front-loading. It is concise without being informative.

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?

For a simple read tool with annotation coverage and no output schema, the description still leaves key questions unanswered: what a terminology/game sheet is, what the return looks like, and how to handle an invalid ID. It is too thin relative to even this modest complexity.

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 the single required parameter sheet_id. The schema's pattern (^sh_[a-f0-9]{20}$) is the only clue to its format, 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.

Purpose3/5

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

The description uses a specific verb ('Read') and resource ('saved terminology/game sheet'), so the basic action is discernible. However, 'terminology/game sheet' is ambiguous — it doesn't clarify what a sheet actually is or how it differs from other retrievable entities like assets or cards.

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?

No guidance on when to use this versus switchboard_sheet_save or the many other *_get siblings. There is no mention of prerequisites, when-not-to-use, or what an agent should do if the sheet is missing.

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