Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_broadcast_pack

Prepare a turnkey Live Broadcast Pack combining Switchboard live order batches, Venue QR Audience Listener URLs, IPTV/LL-HLS #EXT-X-MEDIA alternate audio renditions, and optional Smart-Glasses-to-Dante Cloud ingress binding.

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": {
      "event_id": "<event_id>",
      "title": "<title>"
    },
    "name": "switchboard_broadcast_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
event_idYes
languagesNo
source_kindNo
ttl_secondsNo
bearer_tokenNo
rx_device_idNo
rx_channel_idNo
contributor_idNo
dante_domain_idNo
source_languageNo
duration_minutesNo
verify_route_planNo
switchboard_job_idNo
bridge_tx_device_idNo
bridge_tx_channel_idNo
register_hls_renditionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates external state. The description adds that multiple artifacts are produced in one shot and that the Dante ingress binding is optional, which is real behavioral context. However, it never says what is persisted, whether packs expire (despite a ttl_seconds parameter), or that bearer_token authentication is required.

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 with no filler, and the core verb-resource pair is front-loaded. But the sentence is a dense pile of jargon that is hard to parse on first read, and it spends words on component terminology without stating the outcome or constraints.

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 17-parameter, non-idempotent, open-world composite mutation with no output schema and no parameter documentation, the description is far too thin. An agent cannot tell what the returned pack contains, how long it lives, or what auth it needs before invoking it.

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 17 parameters, so the description carries the full burden and largely fails. It only loosely gestures at a few fields (alternate audio renditions, glasses contributor ingress); required fields like event_id and title, and opaque ones like switchboard_job_id, verify_route_plan, rx_device_id, and register_hls_renditions, get no explanation at all.

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 ('Prepare') and a specific composite resource ('Live Broadcast Pack'), then enumerates the constituent artifacts it bundles: order batches, audience listener URLs, LL-HLS alternate audio renditions, and optional Dante ingress binding. This makes it distinguishable as an aggregator, though it never names a sibling it differs from.

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 call this versus broadcast_live, switchboard_live_open, or the individual switchboard_dante_glasses_bind tool. No prerequisites, no exclusions, no context about what condition makes assembling the whole pack preferable to calling the component tools separately.

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