Skip to main content
Glama

audio_delay

Read or adjust the audio delay in seconds to fix lip-sync issues; positive values play audio later, and omitting the value returns the current delay.

Instructions

Get or set the audio delay in seconds, for fixing lip-sync. Positive values play audio later. Call with no arguments to read the current delay.

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": "audio_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.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does well to disclose the dual read/write mode and the sign convention (positive = audio later). It is silent on persistence of the change, whether it applies live to current playback, and what a read returns, which matter for a mutation-capable tool.

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?

Three short sentences, front-loaded with the core get/set purpose, then the sign semantics, then the read path. Nothing repeats and nothing is wasted.

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-optional-parameter tool with no output schema, the description covers both modes and the value semantics adequately. The remaining gap is minor but real: it never says what a read returns or what happens when `relative` is set without `seconds`.

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; the description earns an extra point by explaining the meaning of the sign of `seconds` (positive plays audio later), which the schema does not state. The `relative` parameter is left entirely to its schema description, and the no-argument read path is largely restated from the schema.

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?

The description gives a specific verb pair and resource (get or set the audio delay), names the unit (seconds) and the problem it solves (lip-sync), which makes it clearly separable from the subtitle_delay sibling by resource rather than by guesswork.

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?

It explicitly covers the read path (call with no arguments), which is the main usage fork for a dual get/set tool, and the lip-sync framing implies when a caller would want it. It stops short of naming subtitle_delay or stating when not to use this tool.

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