Skip to main content
Glama

Subtitle track languages

bpj_html_track_language_audit
Read-onlyIdempotent

Check subtitle track language tags and repeated default tracks on the same media parent.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds real scope information by naming the two specific checks ('language tags' and 'repeated default tracks on the same media parent'), but says nothing about what a finding looks like or how severity is reported.

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?

One compact sentence with the audited subject front-loaded and no filler. It is efficient, though the brevity edges into under-specification rather than being deliberately minimal.

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?

For a read-only audit tool with a single undocumented parameter and no output schema, the description should say what the input is and roughly what the result contains. Neither the input format nor the return shape is described, leaving the agent to guess how to supply text and how to interpret findings.

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 0% and the description never mentions the single required parameter or what it should contain. The agent must infer from the schema's bare title 'Source text' and maxLength of 6000 that raw HTML/markup is expected; the description does not compensate for the coverage gap.

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 ('Check') and two concrete targets: subtitle track language tags and repeated default tracks on the same media parent. An agent can tell this apart from adjacent subtitle tools by scope, but the description never names a sibling or explicitly delimits it from bpj_html_media_caption_tracks or bpj_canonicalize_language_tags.

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 or when-not-to-use guidance and no stated alternatives or prerequisites. The only cue is the implied context of auditing subtitle tracks, which the agent must infer from the purpose sentence alone.

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.