Skip to main content
Glama

Lint a storyboard (preflight, no browser)

lint_storyboard
Read-only

Preflights storyboards before probe/render, flagging scenes that freeze or cut from narration/action mismatch plus selector, wait, and no-op key pitfalls; run after every edit.

Instructions

Browser-free preflight over a storyboard: a per-scene pacing forecast (which scenes compose will mostly freeze-hold or cut because the narration and the recorded action don't match), selector/wait pitfalls (type+Enter with no wait, :text-is on nested labels, focus without a zoom block, anchored waitForChange regexes), and no-op keys. Run it after every storyboard edit, before probe/render. Pass exactly one of dir / path / json. lang lints a narrations[lang] translation at that language's speaking rate.

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

Input Schema

NameRequiredDescriptionDefault
dirNodemo dir → generated/storyboard.json
jsonNostoryboard JSON as a string
langNo
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.

Output Schema

NameRequiredDescriptionDefault
issuesYes
estimateYes
wordsPerSecYes
narrationTotalMsYes

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. Addedv0.14.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds value by stating it is browser-free (no render/launch needed) and by characterizing the output as a forecast of freeze-hold/cut behavior. It doesn't mention cost, limits, or whether it mutates any generated artifacts, so it adds context without full disclosure.

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?

Front-loads the core purpose, then packs the check list into a single readable parenthetical, followed by the operational instruction. Dense but every clause carries information; a slightly heavier scan cost than a clean 5.

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?

With an output schema present and 80% schema coverage, the description needn't explain return values, and it covers the input-selection rules and the lang behavior. The one gap is relational: for a lint/preflight tool sitting next to validate_storyboard, the agent gets no signal on which to choose.

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

Parameters4/5

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

Adds real semantics beyond the schema: the mutual-exclusivity rule ('exactly one of dir / path / json') is not expressed by the schema's optional-but-unconstrained properties, and 'lang lints a narrations[lang] translation at that language's speaking rate' explains the otherwise undescribed lang parameter. The params substitution behavior is left to the schema, which already documents it.

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?

Opens with a specific verb+resource ('Browser-free preflight over a storyboard') and enumerates the concrete check categories it performs (pacing forecast, selector/wait pitfalls, no-op keys), which lets an agent picture the output. It routes positioning against probe/render but never distinguishes itself from the sibling validate_storyboard, leaving the main ambiguity unresolved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Run it after every storyboard edit, before probe/render' gives a clear trigger and pipeline position, and 'Pass exactly one of dir / path / json' states a usage constraint. There is no explicit when-not guidance (e.g., how it differs from validate_storyboard), so it stops short of full alternative routing.

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