Skip to main content
Glama

WebVTT speaker roster

bpj_webvtt_speaker_roster
Read-onlyIdempotent

Count cues by named WebVTT voice annotations, counting each speaker once per cue.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral rule, 'counting each speaker once per cue', which disambiguates the counting semantics. It says nothing about malformed input handling, the 6000-character limit, or the shape of the result.

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 dense sentence with no filler, and the counting rule is front-loaded. Nothing in it is redundant with the name or annotations.

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, so the description carries the burden of explaining return values, and it does not: an agent cannot tell whether the result is a map of speaker to count, a list, or a total. Combined with zero schema coverage on the only parameter, the definition is under-specified for what should be a simple tool.

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% for the single 'text' parameter, so the description has to compensate. Saying it works on 'WebVTT voice annotations' implies the input is WebVTT source, but the description never names the parameter, states that it must be WebVTT-formatted, or mentions the maxLength constraint.

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 names a specific verb and resource: 'Count cues by named WebVTT voice annotations'. That is concrete enough for an agent to distinguish it from conversion siblings like bpj_webvtt_to_srt_cues, but it never explicitly says what it is not or which sibling handles adjacent tasks.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer from the name and one clause that this is the counting tool rather than the parsing or converting tool.

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.