Skip to main content
Glama

Validate a storyboard

validate_storyboard
Read-only

Validates a storyboard against the engine schema without rendering, catching errors before a demo run. Accepts a directory, file path, or JSON string; relaxed mode makes narration optional.

Instructions

Validate a storyboard against the engine schema without running anything. Pass exactly one of: dir (uses generated/storyboard.json), path (a storyboard file), or json (storyboard JSON as a string). relaxed makes narration optional (probe semantics).

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": "validate_storyboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNodemo dir → generated/storyboard.json
jsonNostoryboard JSON as a string
pathNopath to a storyboard .json file
paramsNostoryboard template params (name → value); each must be declared in the storyboard's params block. Substitutes {{name}} across all stages.
relaxedNo

Output Schema

NameRequiredDescriptionDefault
lintNo
titleNo
validYes
issuesYes
warningsYes
sceneCountNo
storyboardPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.20.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / params / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.14.1
    • addedOutput schema / properties / lint
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "action": {
      +        "type": "number"
      +      },
      +      "code": {
      +        "type": "string"
      +      },
      +      "fix": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "scene": {
      +        "type": "string"
      +      },
      +      "severity": {
      +        "enum": [
      +          "error",
      +          "warn",
      +          "info"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "severity",
      +      "code",
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. First observedv0.9.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'without running anything', so the agent knows validation is side-effect free. It also discloses the behavioral effect of 'relaxed' (narration becomes optional, probe semantics), which is genuinely beyond the structured fields. It does not say what a failure looks like, but the output schema covers that.

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?

Three short sentences, front-loaded with purpose and the no-execution guarantee, then the input-selection rule and the relaxed modifier. A little space is spent restating schema descriptions for dir/path/json, but nothing is padded.

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

Completeness5/5

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

With an output schema present, return values need not be described, and the description covers the non-obvious parts: no execution, mutually exclusive input modes, and relaxed semantics. The only mild gap is the undocumented 'params' substitution, which the schema itself explains adequately.

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 coverage is 80%, so the baseline is 3; the description's explanations of dir, path, and json largely restate what the schema already says. The 'relaxed' hint is a real addition, but the 'params' object — the most complex parameter with substitution semantics — is left entirely to the schema.

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 ('Validate a storyboard against the engine schema') plus the important scope qualifier 'without running anything', which distinguishes it from execution tools like render or compose. It does not, however, differentiate itself from the close sibling lint_storyboard or from probe, which the agent could easily confuse it with.

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?

Gives a concrete input-selection rule ('Pass exactly one of: dir, path, or json') and clarifies that nothing is executed, which is useful pre-flight guidance. It never says when to prefer this over lint_storyboard, get_storyboard_schema, or probe, so the agent must infer the boundary from names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.