Skip to main content
Glama

subtitle_bilingual

Display two subtitle tracks at once, usually the original plus a translation, for side-by-side language comparison. Set primary and secondary tracks or auto-pick original and translation.

Instructions

Show two subtitle tracks at once — typically the original plus a translation. Call with no arguments to read the current state. primary is the bottom line and the one subtitle_select refers to; secondary is drawn just above it. Each accepts a track id from subtitle_list or a path to a subtitle file, which is loaded if it is not already. With no tracks named, the original and the translation are picked automatically. Selecting a single track with subtitle_select turns this off.

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

Input Schema

NameRequiredDescriptionDefault
layoutNostacked (just above the first line, the default) or top of the frame
enabledNoTurn it on or off. Omit to read; omitting it while naming a track or layout turns it on.
primaryNoBottom line: a track id, or a path to a subtitle file
secondaryNoThe line above it: a track id, or a path to a subtitle file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the no-argument read mode, the implicit enable-on-write behavior, automatic source selection, and that passing a file path loads the subtitle. It stops short of describing what the read state returns or error behavior for an invalid track id, so it is strong but not exhaustive.

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?

Roughly six short sentences, front-loaded with the core purpose and each adding a distinct fact: read mode, argument semantics, auto-selection, and the interaction with subtitle_select. No filler or restatement of the title.

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 4-parameter, zero-required toggle-style tool with no output schema, the description covers the operations, defaults, and sibling interaction well. The main gap is what the no-argument read actually reports back, which the agent may need to interpret the result.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds genuine meaning: `primary` is the bottom line that subtitle_select refers to, `secondary` renders just above, and both accept either a track id from subtitle_list or a file path that is loaded on demand. That id-versus-path duality and the positional relationship are not obvious from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Show two subtitle tracks at once') and immediately clarifies the typical case (original plus translation). It explicitly positions itself against the sibling 'subtitle_select', so an agent can distinguish the two without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance: call with no arguments to read state, name tracks to turn it on, and 'Selecting a single track with subtitle_select turns this off' defines the mutually exclusive alternative. The auto-pick fallback ('the original and the translation are picked automatically') removes the remaining ambiguity.

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