Skip to main content
Glama

Subtitle line width review

bpj_subtitle_line_width_review
Read-onlyIdempotent

Find individual subtitle lines exceeding a chosen Unicode code point limit.

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>",
      "limit": "<limit>"
    },
    "name": "bpj_subtitle_line_width_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
limitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds only the counting unit (Unicode code points) and says nothing about whether results are returned as an array of offending lines, line indices, or summarized counts, nor about ordering or truncation behavior.

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; the criterion is stated immediately after the action. It is terse rather than bloated, though the terseness is what leaves behavioral gaps.

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?

There is no output schema and no nested objects, yet the description never indicates what the caller receives back (matching lines, their indices, counts). For a two-parameter analysis tool whose only output documentation is absent, this leaves an agent unable to anticipate results or parse them confidently.

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 parameter meaning. It usefully clarifies that 'limit' is measured in Unicode code points rather than bytes or grapheme clusters, which is real added value, but it says nothing about the 'text' parameter's expected format (plain text versus SRT-style cues) despite the 6000-character cap in the 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?

The description states a specific verb and resource ('Find individual subtitle lines') plus the criterion ('exceeding a chosen Unicode code point limit'), which is enough to distinguish this from timing/overlap-oriented subtitle siblings by name and intent. It does not explicitly name or contrast an alternative tool, so this stops short of 5.

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 guidance on when to use this versus the other subtitle tools, no prerequisites, and no note about what to do with the flagged lines. An agent must infer the use case entirely from the one-line purpose statement.

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.