Skip to main content
Glama

SRT timing and CPS stats

srt_stats

Summarizes an SRT document with cue count, total and average durations, first-to-last span, and per-cue character counts and CPS, helping you check subtitle timing and reading speed.

Instructions

Summarise an SRT document: cue count, total on-screen duration, span from first start to last end, average and max characters-per-second, and a per-cue breakdown of start/end, duration, character count, and CPS. Uses the same grapheme rules as lint_srt.

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": {
      "srt": "<srt>"
    },
    "name": "srt_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
srtYesFull SRT file contents
maxCpsEnNoMax characters per second for Latin cues (default 21)
maxCpsCjkNoMax characters per second for CJK cues (default 9)
maxCharsEnNoMax characters per Latin line (default 42)
maxCharsCjkNoMax characters per CJK line (default 16)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of the return value well and flags grapheme-based counting consistency with lint_srt, but it never explains what the maxCpsEn/maxCpsCjk/maxCharsEn/maxCharsCjk thresholds actually do to the output (presumably flagging over-limit cues) or whether they affect only the per-cue breakdown.

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?

Two sentences, front-loaded with the verb and resource and then the computed metrics; virtually every clause carries information. Slightly list-heavy but appropriate for enumerating a return shape that has no output 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?

With no output schema and no annotations, the description compensates by enumerating the returned metrics in detail, which is the critical missing structured data. The remaining gap is behavior of the four threshold parameters and whether exceedances are reported, which an agent would still need to discover by calling the tool.

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 four optional threshold parameters and the required 'srt' body are already documented with defaults in the schema, making 3 the baseline. The description adds only the grapheme-counting rule, which is genuinely useful for interpreting character counts, but it does not clarify how the limit parameters alter the results.

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?

Specific verb ('Summarise') plus resource ('an SRT document') followed by an enumeration of exactly what is computed: cue count, total on-screen duration, span, average/max CPS, and a per-cue breakdown. The reference to lint_srt's grapheme rules implicitly positions this as the reporting counterpart to the linting tool, so an agent can tell the two apart.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance; the lint_srt mention is about grapheme-rule parity, not routing. The agent must infer that this tool is for reporting metrics whereas lint_srt finds violations, without the description ever saying so.

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