Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_dante_status

Read-onlyIdempotent

Read Audinate Dante Managed API control-plane readiness without contacting a vendor endpoint.

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": "switchboard_dante_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
bearer_tokenNo

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, idempotentHint and destructiveHint=false, so safety is covered elsewhere. The description does add one genuine behavioral fact beyond them: the check is answered locally rather than by calling a vendor endpoint, which explains why it is safe and cheap to poll. It stops short of saying whether the result reflects live device state or a cached snapshot, and there is slight tension with openWorldHint=true that is never resolved.

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?

One front-loaded sentence with no filler, and the key qualifier ('without contacting a vendor endpoint') lands early. It is efficient, though brevity here comes at the cost of the missing operational detail noted elsewhere.

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?

With no output schema, the description carries the burden of explaining what a 'readiness' result contains, and it does not. For a zero-required-parameter diagnostic this is workable but incomplete; the agent knows the tool is a safe local read but not what it will learn from 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% and the single optional parameter 'bearer_token' (16-4096 chars) is not mentioned at all in the description. An agent is left to guess when credentials are required, whether the token must be a Dante-specific credential, or what happens if it is omitted.

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?

The verb 'Read' and the object 'Dante Managed API control-plane readiness' are stated, but 'readiness' is never defined, so an agent cannot tell what the returned state actually represents. It partially differentiates from siblings like switchboard_dante_bridge_status and switchboard_dante_domain_get by scoping itself to the control plane, but that distinction is left implicit.

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 when-to-use guidance, no preconditions, and no named alternative. The phrase 'without contacting a vendor endpoint' hints at a diagnostic use case but never says what task should route here versus to switchboard_dante_bridge_status or switchboard_dante_domain_get.

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