Skip to main content
Glama

Subtitle silence intervals

bpj_subtitle_silence_intervals
Read-onlyIdempotent

Merge overlapping cue intervals and report uncovered gaps between the first and final cues.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description usefully adds that overlapping intervals are merged (i.e. deduplicated) and that gaps are only reported between the first and final cues, which is real behavioral context. It does not disclose output shape, whether gap values are in seconds or frames, or any input format assumptions.

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?

A single tight sentence with the operation front-loaded and no filler. Nothing is wasted, though brevity here borders on under-specification given the untyped input.

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, the description carries the burden of explaining what comes back, and it only gestures at 'gaps' without units or shape. Combined with an undocumented text format, an agent cannot confidently construct a call or interpret the result from this definition alone.

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% and the only parameter is a bare 'text' string capped at 6000 characters, yet the description never mentions the input at all. It is unclear whether the text should be SRT, WebVTT, or a custom cue notation, which is a critical omission when the single input is entirely untyped beyond 'string'.

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 specific operations (merging overlapping cue intervals, reporting uncovered gaps) against a specific resource (subtitle cues), so the transformation is clear. It stops short of differentiating itself from close siblings like bpj_subtitle_overlap_window, leaving ambiguity about which tool an agent should pick for overlap handling.

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 prerequisites, and no routing to or away from alternatives such as bpj_subtitle_overlap_window or bpj_subtitle_clock_drift. The agent must infer the use case entirely from the verb phrase.

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.