Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

title_manifest_validate

Validate title manifests for normalized boxes, valid cue types, positive frame rate, and accurate frame timing.

Instructions

Validate a title manifest for normalized boxes, valid cue types, positive frame rate, and frame timing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "title_manifest_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
manifestNo
manifest_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the validation criteria (boxes, cue types, frame rate, timing), which is useful behavioral context, but it omits what happens on failure, whether mutations occur, or any return value details.

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?

The description is a single sentence of 15 words, front-loaded with the action and resource. It is concise and without filler, though it could be expanded to include invocation context.

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?

Given the complexity of the nested manifest object and the absence of an output schema, this description is under-specified. It does not explain the return format, what 'normalized boxes' means, or how to choose between manifest and manifest_path, leaving the agent with insufficient information for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description provides no explanation of the three parameters (id, manifest, manifest_path). The agent cannot determine whether to pass a manifest object or path, what 'id' refers to, or how the nested structure is used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Validate' and resource 'title manifest', and lists concrete validation aspects (normalized boxes, valid cue types, positive frame rate, frame timing). This clearly differentiates it from sibling tools like title_manifest_create or title_manifest_adjust.

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 description implies this tool is for checking a manifest before use, but provides no explicit when-to-use guidance, alternatives, or exclusions. The usage context is only implied by the verb 'validate'.

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