Skip to main content
Glama

set_speed

Read or change the playback speed of the video window being watched, using an absolute multiplier or a relative offset, with pitch correction keeping speech natural.

Instructions

Get or set the playback speed of the window the user is watching. Call with no arguments to read the current rate. Pitch is corrected by default, so speech stays natural — see the pitch CLI command to turn that 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": "set_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoSpeed multiplier between 0.01 and 100 (e.g. 1.5). Omit to read the current rate.
relativeNoTreat `rate` as an offset from the current speed instead of an absolute multiplier. Clamped to the valid range.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 behavioral burden. It usefully discloses that pitch is corrected by default and points to the pitch command to disable that behavior. However, it does not explain persistence, scope beyond the current window, or what happens to speed when switching videos, leaving meaningful behavioral gaps.

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?

Two tightly written sentences with no wasted words. The get/set distinction is front-loaded, and the pitch correction note is compact and relevant.

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 simple two-parameter tool with no output schema, the description covers the essential read/set behavior and the notable pitch-correction default. It could say more about how the current rate is returned, but that gap is minor for this complexity level.

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%, so the schema already documents the rate range and the relative offset behavior. The description adds only that omitting arguments reads the current rate, which is useful but not beyond what the schema already conveys. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: get or set the playback speed of the window the user is watching. It clearly distinguishes reading from setting via the no-argument behavior. It does not explicitly contrast with sibling tools such as set_volume, but the purpose is unambiguous.

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 says to call with no arguments to read the current rate, which gives clear guidance for the read use case. Setting is implied when arguments are supplied. It does not discuss when not to use it or explain the relative parameter's usage, but the core when-to-use signal is present.

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