Skip to main content
Glama

Subtitle reading pace

bpj_subtitle_reading_pace
Read-onlyIdempotent

Compute characters per second for each cue, excluding whitespace and simple inline tags.

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": {
      "text": "<text>"
    },
    "name": "bpj_subtitle_reading_pace"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so safety is covered. The description usefully adds the counting rule (whitespace and simple inline tags excluded), but it does not say how 'cues' are delimited in the input or what the return structure looks like, which matters for a pure-computation tool.

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?

One front-loaded sentence with no filler; the exclusions are stated compactly. It is appropriately sized for a single-purpose calculator, though brevity here comes partly at the cost of missing detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 0% schema description coverage, the description carries the burden of explaining input format and result shape, and it does neither. For a tool whose behavior depends entirely on how cues are recognized in a 6000-character blob, that is a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'text' parameter, and the description never clarifies whether that text is SRT, WebVTT, or plain lines — the very thing that determines how cues are parsed. It adds the exclusion rule but not the input format the caller must supply.

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?

States a specific verb and metric: 'compute characters per second for each cue', which separates it from the adjacent bpj_reading_length_estimate (length, not rate). It does not explicitly name that sibling, so differentiation relies on the metric noun rather than on routing language.

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 when-to-use guidance, no mention of thresholds or standards (e.g. typical cps limits), and no exclusions pointing to bpj_reading_length_estimate or bpj_subtitle_line_width_review. The agent must infer the use case entirely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.