Skip to main content
Glama

Subtitle overlap windows

bpj_subtitle_overlap_window
Read-onlyIdempotent

Sort cues by start time and identify overlap with the longest active preceding cue.

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_overlap_window"
  }
}

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?

The readOnlyHint, idempotentHint and destructiveHint=false annotations already establish the safety profile, so the bar is lower. The description adds the actual algorithm (ordering by start time, comparing against the longest preceding active cue), which is useful. It doesn't say what comes back — a list of overlaps, count, modified cues — and there is no output schema to fill that gap.

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?

The description is a single front-loaded clause with no filler, so nothing is wasted. It is tight to the point of under-specification, but the structure itself is clean.

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 an undocumented parameter, the description should carry the return format and the input format. It covers neither, so it is materially incomplete for a text-processing tool that could accept several subtitle container formats.

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?

There is exactly one parameter, 'text', and the schema gives it 0% description coverage. The description refers to 'cues', hinting that the input is cue-based subtitle text, but it never states the expected format (SRT, WebVTT, or otherwise). That is the main thing an agent needs in order to call it correctly, and it is missing.

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?

The description names a specific operation: sorting subtitle cues by start time and finding overlap with the longest active preceding cue. That tells an agent exactly what computation runs. However, it never says what separates this from bpj_time_window_overlap or bpj_subtitle_clock_drift, so it doesn't distinguish itself from its siblings.

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?

The description says what the tool computes but never says when to reach for it, what precondition must hold (for example, that the text must be cue-based subtitle data), or which alternative fits another case. An agent has to infer usage from the name alone.

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.