Skip to main content
Glama
Sign In
demo-vid-mcp

demo-vid-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

demo_vid_script_validate

Validate a narration script's structure and timing, checking for required fields and reasonable timings to ensure valid formatting.

Instructions

Validate a narration script for structure and timing.

Checks that the script has required fields ('steps'), each step has an 'action',
and timing values are reasonable.

## Return Format
{"success": bool, "message": str, "errors": list | None}

## Examples
await demo_vid_script_validate(script_yaml="title: Test

duration_target: 30 steps:

  • action: goto url: / wait: 2 ")

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": {
      "script_yaml": "<script_yaml>"
    },
    "name": "demo_vid_script_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
script_yamlYesYAML narration script content.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 mentions checks for required fields and reasonable timing but does not disclose if the tool is read-only, whether it has side effects, or its behavior on validation failure (e.g., does it raise errors?). The description adds some behavioral context but lacks depth for a validation tool.

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 concise with about 5 lines of prose plus a return format specification and example. It front-loads the core purpose and uses markdown headers for structure. No superfluous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only one parameter (with 100% schema coverage), an output schema, and a clear validation purpose, the description covers the essentials. It provides return format and an example, but could add more context about error types or edge cases. General advice is addressed, but still complete enough for typical use.

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 100%, so baseline is 3. The description adds minimal value by stating the script must be YAML and listing expected fields like 'steps' and 'action', but does not elaborate on the parameter format or constraints beyond what the schema provides.

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 clearly states the tool validates a narration script for structure and timing, specifying the required fields and checks. It distinguishes itself from siblings like demo_vid_script_draft (which drafts scripts) and demo_vid_generate (which generates videos) but does not explicitly differentiate from all siblings.

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 use when you need to validate a script before generating a video, but it does not explicitly state when to use this tool versus alternatives like demo_vid_help for general help or demo_vid_refine for refinement. No when-not-to-use or alternative guidance is provided.

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