Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
lint_srtA

Parse a SubRip (.srt) document and return diagnostics for cue numbering, invalid or odd timestamps, end-before-start (negative duration), zero duration, overlaps, reading speed (CPS), line length, empty cues, too many lines, and WebVTT mislabelled as SRT. Character counts use Intl.Segmenter graphemes and ignore simple subtitle markup.

fix_srtA

Apply only safe, mechanical fixes to an SRT document: renumber cues to 1…n (inserting a missing index), normalize timestamps to HH:MM:SS,mmm, and wrap long lines at spaces (English) or at a character (CJK). Does not change overlaps, negative/zero duration, or high CPS — those need a human look. Returns the updated SRT text and remaining issue counts.

srt_statsB

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

Each tool has a distinct role: lint_srt returns diagnostics, fix_srt applies mechanical repairs, and srt_stats returns a quantitative summary. There is partial overlap since CPS, character counts, and line length surface in both lint_srt and srt_stats, but the output framing (problems vs. metrics) keeps them separable.

Naming Consistency4/5

lint_srt and fix_srt follow a clean verb_noun pattern, while srt_stats breaks it with a noun-first form. The deviation is minor and the subject (srt) is consistent across all three, so the set remains predictable.

Tool Count4/5

Three tools is lean but each maps to a genuine operation (diagnose, repair, summarise) for a narrow SRT-focused domain. There is little dead weight, though the surface is close to the thin end.

Completeness4/5

The diagnose/fix/measure lifecycle covers the core SRT workflow, and fix_srt deliberately scopes to safe fixes. Gaps are minor: no selective or per-issue-type fixing, no format conversion (e.g. WebVTT output), and no re-validation pass bundled with fixes.