Skip to main content
Glama

audio_select

Select an audio track by ID to control playback audio; set the ID to 0 to disable audio entirely.

Instructions

Select an audio track by ID (0 to disable audio)

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": {
      "id": "<id>"
    },
    "name": "audio_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAudio track ID (0 to disable)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add one genuinely useful behavioral fact: ID 0 disables audio rather than selecting a track. It says nothing about invalid IDs, whether the change takes effect immediately during playback, or whether selection persists, which leaves notable gaps for a state-changing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the core action and the key special value front-loaded, plus a parenthetical that earns its place. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter selection tool with no output schema and full schema coverage, the definition is nearly sufficient; the disable semantics are captured. The remaining gap is how to obtain valid IDs (presumably audio_list), which an agent would need to avoid guessing an index.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter already documents 'Audio track ID (0 to disable)', so the description adds no meaning beyond the schema. Baseline 3 applies when the schema does the work.

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 (Select) and resource (audio track) plus the identifier used, so the agent knows exactly what the tool does. It does not name or differentiate itself from the sibling audio_list, which is the natural companion for discovering valid IDs, so it falls short of a 5.

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: nothing says to call audio_list first to obtain a valid track ID, or what happens relative to subtitle_select or audio_delay. The only usage cue is the parenthetical '0 to disable audio', which hints at a special case but is not guidance about choosing this tool over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools