Skip to main content
Glama
Sign In
Foldline

Foldline

by alireza12t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Make an SRT file

make_subtitles

Writes an .srt subtitle file from timed cues, converting start/end times and text into a ready-to-use subtitle track for videos.

Instructions

Writes an .srt subtitle file from 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": {
      "cues": "<cues>",
      "out": "<out>"
    },
    "name": "make_subtitles"
  }
}

Input Schema

NameRequiredDescriptionDefault
outYesPath of the .srt.
cuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses only that a file is written; it does not say whether an existing .srt at the same path is overwritten, whether parent directories are created, what text encoding or line-ending format is used, or whether the write is reversible. For a filesystem mutation tool this is a substantial 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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness edges toward under-specification rather than genuinely earned brevity.

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 annotations, no output schema, and an undocumented cue timestamp format, the definition leaves an agent guessing on the details most likely to cause a wrong call. The only complete piece of information is the output path parameter, which the schema already covers.

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 only 50%: 'out' is documented in the schema, but the 'cues' array and especially its 't0'/'t1' numbers have no description anywhere. The description names 'cues' but adds no meaning — the critical ambiguity of whether timestamps are seconds, milliseconds, or frames is left unresolved in both description and schema.

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 concrete verb and resource: 'Writes an .srt subtitle file from cues.' An agent can immediately tell this produces a subtitle file, which is distinct from siblings like make_voice or render_video. It stops short of an explicit contrast with any sibling, so it is clear but not differentiated by name.

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?

The phrase 'from cues' implies the tool is the one to call when you already have timed cue data, which is a usable usage signal. There is no explicit when-not guidance, no mention of prerequisites such as cue timing units, and no named alternative for related tasks like generating voice or exporting events.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools