Skip to main content
Glama

Shift subtitle timing

bpj_subtitle_shift_timeline
Read-onlyIdempotent

Shift every SRT cue by a signed millisecond offset and reject negative resulting timestamps.

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>",
      "offset": "<offset>"
    },
    "name": "bpj_subtitle_shift_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavior beyond that: negative resulting timestamps are rejected rather than clamped or wrapped. It does not say what happens if the input is not valid SRT or whether the full text is returned.

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 sentence that front-loads the transformation and appends the one non-obvious constraint. No filler, nothing repeated from structured fields.

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

Completeness3/5

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

For a two-parameter pure transformation with no output schema, the description covers what is done and one error rule, which is close to adequate. It is missing the return shape (shifted SRT text presumably) and malformed-input behavior, which matter for calling it correctly.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry meaning, and it does add two things: 'text' is SRT cue data (not arbitrary text) and 'offset' is signed with rejection semantics for negative results. It still says nothing about the ±3600000 bounds, the 6000-character limit, or output form.

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 (shift) and resource (every SRT cue) plus the unit and sign of the offset, so the operation is unambiguous. It does not distinguish itself from subtitle siblings such as bpj_subtitle_clock_drift or bpj_subtitle_overlap_window, leaving differentiation to inference.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. An agent must guess whether this is the right subtitle tool for retiming versus drift detection or pace review.

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.