Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_live_feed

Read-onlyIdempotent

Read the contiguous terminal phrase feed. Use after=-1 for full catchup, then the last returned index.

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": {
      "job_id": "<job_id>"
    },
    "name": "switchboard_live_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
job_idYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds real behavioral value by disclosing the contiguous/append-only nature of the feed and the cursor protocol for catchup, but it never describes the return payload, feed termination, or whether reads block. With annotations doing the heavy lifting, a 3 is fair.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and immediately followed by the operational rule. Nothing is redundant or 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 read-only feed tool with no output schema and 0% schema description coverage, the definition should say what the feed returns and whether reads terminate or block. It covers the cursor mechanics but leaves output shape and job_id/language intent implicit, which is inadequate given the undocumented parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden, and it only explains one of three parameters: 'after' gets precise sentinel semantics (-1 = full catchup, otherwise last returned index). 'job_id' and 'language' are left entirely to their patterns and names, which is a partial compensation but not complete.

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 ('Read') applied to a named resource ('contiguous terminal phrase feed'), which is enough to separate it from switchboard_live_say/close/extend without inspecting those schemas. It stops short of naming the sibling alternatives or clarifying what 'terminal' means in this feed context.

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?

Gives a concrete procedural rule: start with after=-1 for full catchup, then advance using the last returned index. It offers no guidance on which sibling to pick (e.g., live_extend vs live_close while reading) or when to stop polling, so usage is implied rather than fully scoped.

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