Skip to main content
Glama

subtitle_delay

Get or set subtitle delay in seconds to sync subtitles with dialogue, with positive values showing subtitles later. Call without arguments to read the current delay; use relative offsets to correct drift.

Instructions

Get or set the subtitle delay in seconds. Positive values show subtitles later. Call with no arguments to read the current delay. Useful for correcting AI-generated subtitles, which often drift a few hundred milliseconds from the dialogue.

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_delay"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsNoDelay in seconds. Omit to read the current value.
relativeNoTreat `seconds` as an offset from the current delay instead of an absolute value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals the dual read/write contract and the sign convention, but says nothing about whether a subtitle must already be loaded, whether the setting persists across sessions or subtitle reloads, or whether it applies retroactively to a currently displayed track — material facts for a player-mutating tool.

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?

Three tight sentences, front-loaded with the get/set contract before the sign convention and the read-mode hint. The AI-subtitle rationale is a usage cue that earns its place, though it could be trimmed without loss.

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 two-parameter, zero-required tool with no annotations and no output schema, the description covers mode selection, units, sign semantics, and a read path. The remaining gaps (preconditions such as an active subtitle track, persistence of the setting) are moderate but real for a mutating player control.

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 100%, so the baseline is 3, and the description earns above it by adding the semantic interpretation of the `seconds` value (positive shows subtitles later) and reiterating that omitting it triggers a read rather than a write. It does not elaborate on the interaction between `seconds` and `relative`, which the schema covers only briefly.

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 specific paired verb (get/set) and resource (subtitle delay) with units in seconds and the sign convention. The resource is unambiguous against the parallel audio_delay sibling, and the no-argument read mode is spelled out so an agent can tell the two modes apart immediately.

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

Usage Guidelines4/5

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

Gives a clear when-to-use context (correcting AI-generated subtitles that drift a few hundred milliseconds) and explicitly states the read path: call with no arguments. It does not set boundaries against the closest sibling (audio_delay) or say when not to adjust delay, so it falls short of full alternative routing.

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