Skip to main content
Glama

generate_chapters

Creates chapters from transcript pauses for files without chapters, adding navigation that appears in chapter lists, marks the progress bar, and supports chapter seeking.

Instructions

Give a file that has no chapters a set of them, derived from the pauses in its transcript. The result becomes real navigation: it shows up in chapter_list, marks the progress bar, and responds to chapter_seek. This is a rough heuristic — if you have read the transcript, set_chapters will give better titles and boundaries.

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

Input Schema

NameRequiredDescriptionDefault
countNoRoughly how many chapters to aim for (2-50, default 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 well: it discloses the heuristic nature, warns that output quality is rough, and enumerates the downstream effects (visible in chapter_list, progress bar, chapter_seek). It stops short of saying what happens if the file already has chapters or whether the operation is reversible (clear_chapters exists but is not referenced), which matters for a mutation 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 sentences, front-loaded with the precondition and action, then effects, then the caveat/alternative. Every sentence contributes distinct information with no filler.

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 one-optional-parameter tool with no output schema and no annotations, the description covers purpose, effects, quality expectations, and the alternative route. Missing only the edge-case behavior around pre-existing chapters and what is returned, which keeps it short of full completeness.

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?

The single parameter has full schema description coverage (range 2-50, default 8), so the schema already documents it. The description only implies that the value is a target rather than an exact count via 'derived from pauses'; it adds no format or behavioral detail beyond the schema, so baseline 3 applies.

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 action (generating chapters) on a specific resource (a file lacking chapters) and names the derivation source (pauses in the transcript). It also implicitly separates itself from set_chapters by framing itself as the heuristic/fallback path, so an agent can pick between the two without opening either schema.

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?

Explicitly names the situation to use it (file has no chapters) and the alternative plus the condition that selects it (if you have read the transcript, use set_chapters for better titles and boundaries). This is exactly the when/when-not/alternative guidance the dimension asks for.

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