Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_asset_get

Read-onlyIdempotent

Resolve one private audio asset from your job receipt. Download the returned URL through the existing audio API; no media generation or payment.

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>",
      "file": "<file>"
    },
    "name": "switchboard_asset_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
job_idYes
read_keyNo
credit_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the return shape (a URL, not the media itself), the downstream step needed to download it, and that no generation work or payment is triggered. It still omits failure modes and credential handling, which keeps it short of a 5.

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 tight sentences with the purpose front-loaded and no filler; the "no media generation or payment" clause earns its place by preventing a costly misread. The middle clause about the existing audio API is slightly awkward but carries necessary information.

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?

With no output schema, four parameters at 0% schema coverage, and regex-only constraints, the description leaves too much unspecified: credential handling, optionality of read_key and credit_key, and error behavior are all absent. What it does cover (the returned URL and the no-charge guarantee) is useful but not enough for a four-parameter retrieval tool.

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%, so every parameter is documented only by a regex pattern. The description never explains what read_key or credit_key are, whether they are credentials, when they are required, or how the file argument relates to the asset being resolved. With four undocumented parameters, the description does not compensate for the coverage gap.

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?

"Resolve one private audio asset from your job receipt" states a specific verb and resource and scopes it to a single asset tied to a prior job. It is reasonably distinguishable from listing-style siblings like switchboard_media or switchboard_job_get, though it never names an alternative to sharpen the contrast.

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?

"From your job receipt" implies the job_id must come from a prior job, and "no media generation or payment" rules out treating this as a creation or billing call. However, there is no explicit statement of when to prefer this tool over siblings such as switchboard_media or switchboard_job_get, so usage remains inferred rather than stated.

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