Skip to main content
Glama

Subtitle clock drift correction

bpj_subtitle_clock_drift
Read-onlyIdempotent

Rescale cue times using source and target running lengths and round to milliseconds.

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>",
      "original": "<original>",
      "target": "<target>"
    },
    "name": "bpj_subtitle_clock_drift"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
targetYes
originalYes

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 the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description only needs to add transform behavior. It does disclose the rounding policy ('round to milliseconds'), which matters for output fidelity, but it says nothing about what the tool returns (rewritten text vs. a list of new times) or whether original/target must differ.

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 sentence, front-loaded with the action and free of filler. It is efficient rather than bloated; the brevity is close to 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?

For a three-required-parameter text transformation with no output schema and no schema descriptions, the definition leaves the text format, the returned value, and edge-case behavior (e.g., original == target, malformed cues) unaddressed. What is present is accurate but insufficient for an agent to call it confidently without guessing.

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% – the schema carries only titles – so the description is the sole source of parameter meaning. It clarifies that 'original' and 'target' are running lengths driving a proportional rescale, but it never defines the expected format/contents of the required 'text' parameter (SRT? VTT? raw cues?) despite its 6000-character limit, and it does not state the scale relationship (target/original) explicitly.

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 verb ('Rescale') and target ('cue times') and states the exact inputs that drive the transform ('source and target running lengths'). This implicitly distinguishes it from a shift/re-shift tool like bpj_subtitle_shift_timeline, but it never names or contrasts a sibling explicitly.

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: nothing says this is for correcting a change in total running time rather than offsetting a constant delay, and no preconditions or alternatives are stated. An agent must infer the drift-correction scenario from the name and the original/target pair 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.