Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_sheet_save

Idempotent

Save an optional terminology/game sheet through the existing API.

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": "<sheet>"
    },
    "name": "switchboard_sheet_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetYes

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 this is a non-read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds almost nothing beyond that: it does not say whether the save overwrites, merges, requires auth, or validates content.

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?

It is a single sentence, so it is short, but 'optional' is misleading given the required parameter and 'through the existing API' is filler that does not earn its place.

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 mutation tool taking an unconstrained nested object with no output schema and no parameter documentation, the description is far too thin. An agent cannot know what to put in 'sheet' or what saving it will do to existing data.

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 coverage is 0% and the single parameter is a free-form nested object with additionalProperties allowed, so the description is the only source of meaning. 'Terminology/game sheet' hints at content, but gives no key structure, expected fields, or examples needed to populate it.

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?

Names a verb and resource ('Save ... sheet'), which is better than a tautology, but 'optional terminology/game sheet' is ambiguous and the word 'optional' conflicts with the schema's required 'sheet' parameter, muddying what is actually being saved.

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 statement of when to use this versus switchboard_sheet_get or any other sibling, no preconditions, and no mention of what happens on subsequent saves. 'Through the existing API' provides no actionable context.

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