Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

broadcast_live

Read-onlyIdempotent

Live broadcast stream access (per session, active shows only) Unpaid calls return HTTP 402 requirements; retry with payment_signature.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "broadcast_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_refNo
credit_keyNo
wallet_proofNo
wallet_addressNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: unpaid invocations fail with HTTP 402 and carry payment requirements that must be satisfied by retrying with payment_signature. That retry/402 contract is exactly the kind of operational context annotations cannot express. It stops short of describing what the returned stream looks like or whether a retry consumes credits.

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?

Two short sentences with no filler, and the payment-failure behavior is front-loaded in the second sentence. Minor deduction for the run-on parenthetical and missing sentence separation between the scope clause and the payment clause.

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?

Payment failure handling is covered, which is the hardest part of this tool, but with five undocumented parameters, no output schema, and no indication of return shape for a stream-access call, an agent still lacks enough to invoke it correctly on the first attempt.

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 parameters, so the description carries the full burden — yet it only clarifies payment_signature (used on retry). order_ref, credit_key, wallet_proof, and wallet_address are given no meaning in prose, leaving most inputs to be guessed from names and regex patterns alone.

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?

"Live broadcast stream access" identifies the resource (live broadcast stream) but the verb is vague — access could mean fetch a stream URL, subscribe, or read feed metadata, and the sibling set includes switchboard_live_feed and switchboard_live_open which an agent cannot disambiguate from this wording. The parenthetical narrows scope to per-session active shows, which helps, but the core action remains underspecified.

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?

The description gives a scoping condition (per session, active shows only) and a retry path after payment, but never states when to choose this tool over switchboard_live_feed, switchboard_live_open, or broadcast_sponsor. There is no explicit when-to-use or when-not-to-use guidance.

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