Skip to main content
Glama

srt verify

srt-verify
Read-onlyIdempotent

Verify subtitles/timing (QC), pure-logic Price: $0.05 per call, USDC on Base via x402.

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": {
      "srt": "<srt>"
    },
    "name": "srt-verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
srtYesstring (SRT text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds genuinely new context — the $0.05 per-call price, USDC on Base via x402 payment, and 'pure-logic' (no external service). It still omits what verification produces (pass/fail vs. issue list) and any limits on input size.

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?

Very short and front-loaded, with the purpose stated first. The pricing clause is crammed in without punctuation, making the sentence read as a run-on, but nothing is redundant.

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 one-parameter read-only tool this is mostly sufficient, especially with annotations covering safety. However, with no output schema the description should say what a 'verify' result looks like, and it does not — an agent cannot predict whether it receives a boolean, an error list, or a score.

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?

There is a single parameter with 100% schema description coverage, which sets the baseline at 3. The description implies the input is subtitle text with timing, matching the schema's 'srt' string, but adds no format, encoding, or size constraints beyond that.

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 and resource: 'Verify subtitles/timing (QC)'. No sibling tool touches subtitles, so an agent can distinguish it from the crypto/analysis siblings without opening the schema. The purpose is clear, though 'verify' leaves the checks performed unspecified.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only usage signal is the parenthetical '(QC)', which merely implies quality-check workflows. An agent gets no routing logic beyond the tool name.

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.

Resources