Skip to main content
Glama

set_chapters

Add a chapter list to a file that lacks chapters by supplying titles and start times in seconds; marks are sorted, clamped, and become navigable chapters on the progress bar.

Instructions

Set the chapter list for a file that has none, from your own reading of its content. Times are in seconds; they are sorted and clamped to the file automatically. These become real chapters — navigable with chapter_seek and drawn on the progress bar. Fails if the file already ships with its own chapters.

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": {
      "chapters": "<chapters>"
    },
    "name": "set_chapters"
  }
}

Input Schema

NameRequiredDescriptionDefault
chaptersYesChapter marks in playback order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it well: it discloses automatic sorting and clamping, the seconds unit, that the marks become real navigable chapters drawn on the progress bar, and the exact failure condition. It omits whether the call requires the file to be loaded/selected or what happens on an invalid time value.

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?

Four short sentences, each doing distinct work: scope, unit and normalization, observable effect, failure mode. The precondition is front-loaded and there is no redundant restatement of the schema.

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 single-parameter mutation tool with no annotations and no output schema, the description covers preconditions, normalization behavior, downstream effects, and error conditions. Only the return value and any required file-selection state are left unstated.

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 coverage is 100%, with both nested fields ('time' in seconds, 'title') already documented in the schema, so the baseline is 3. The description only adds the sorting/clamping behavior, which is operational rather than per-parameter meaning.

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 verb and resource ('Set the chapter list for a file') and adds a hard scope constraint ('that has none, from your own reading of its content') that separates it from generate_chapters and clear_chapters. An agent can identify the operation and its precondition without opening the schema.

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 applicability condition — the file must have no chapters — and reinforces it with the failure case at the end. It stops short of naming the sibling to use instead (generate_chapters for auto-generation, clear_chapters to remove), so the routing is implied rather than explicit.

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