Skip to main content
Glama

SRT to WebVTT

bpj_srt_to_webvtt
Read-onlyIdempotent

Convert SRT cue timings and multiline captions into a WebVTT document.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the conversion handles cue timings and multiline captions, but it does not describe validation behavior, how malformed SRT is handled, or output formatting details beyond the WebVTT document type.

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?

The description is a single front-loaded sentence with no filler. It identifies the source format, the content handled, and the output format efficiently.

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

Completeness4/5

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

For a simple one-parameter converter with rich annotations and no output schema, the description is largely complete: it names the input domain and states that the result is a WebVTT document. It could add a little more about malformed-input behavior or formatting preservation, but none of that is critical for this tool's complexity.

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

Parameters4/5

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

There is only one parameter, text, and the schema has 0% description coverage, but the description clarifies that the input should contain SRT cue timings and multiline captions. That adds useful domain meaning beyond the schema's type and title, though it does not restate requiredness or the maxLength constraint, which remain in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: convert SRT cue timings and multiline captions into a WebVTT document. The direction of conversion is explicit, which distinguishes it from the reverse sibling bpj_webvtt_to_srt_cues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the conversion description: call this when you have SRT content and need WebVTT. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of the reverse conversion tool or any preconditions.

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.