Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_dante_glasses_bind

Authorize a smart-glasses (LiveLens), station-desk, or Switchboard return session to feed a Dante Cloud TX channel and mint a scoped ingress token.

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": {
      "domain_id": "<domain_id>",
      "bridge_tx_device_id": "<bridge_tx_device_id>",
      "bridge_tx_channel_id": "<bridge_tx_channel_id>"
    },
    "name": "switchboard_dante_glasses_bind"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
room_idNo
languageNo
domain_idYes
source_kindNo
ttl_secondsNo
bearer_tokenNo
rx_device_idNo
rx_channel_idNo
contributor_idNo
verify_route_planNo
switchboard_job_idNo
bridge_tx_device_idYes
bridge_tx_channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=true, idempotent=false, so the safety profile is covered. The description adds genuinely new behavioral information: it mints a scoped ingress token, i.e. a credential-issuing side effect. It does not say what happens on repeated binds (relevant given idempotent=false), what auth the bearer_token supplies, or how token scope/TTL behaves.

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?

A single front-loaded sentence with no filler; the source kinds and the target channel are named before the token-minting consequence. It is tight, though for a 14-parameter tool the compression leaves the reader with nothing to hang parameter meaning on.

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?

Fourteen parameters with 0% schema description coverage and no output schema, yet the description explains only source_kind and the required TX device/channel. mode (direct_pcm vs switchboard_translate), ttl_seconds, bearer_token, verify_route_plan, room_id, contributor_id, switchboard_job_id and the rx_* pair are all left entirely undocumented.

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

Parameters4/5

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

Defaults to baseline 4 for a zero-parameter tool.

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?

Uses a specific verb ('Authorize') on a specific resource pairing: a LiveLens/station-desk/Switchboard-return session feeding a Dante Cloud TX channel, plus token minting. That is enough to tell it apart from siblings like switchboard_dante_glasses_frame or switchboard_dante_route_plan, though no sibling is named as the contrasting alternative.

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 explicit when-to-use or when-not-to-use guidance and no stated prerequisites, sequencing (e.g. route_plan before bind), or relationship to the close/frame siblings. The use case is only inferable from the effect described, which is the same weakness seen in comparable 'just says what it does' definitions.

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