Skip to main content
Glama

Generate a free documentary storyboard preview

create_storyboard_preview

Research a topic on Wikipedia and generate an 8–12 shot documentary opening storyboard with narration script, archive Wikimedia Commons CC-licensed images, maps and number cards (~25 seconds). Free (counts toward daily account preview limit).

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": {
      "topic": "<topic>"
    },
    "name": "create_storyboard_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional angle or era notes (up to 280 chars).
topicYesDocumentary topic line (3–140 chars), e.g. "The night Krakatoa exploded".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover open-world access and non-read-only, non-idempotent behavior; the description adds genuinely new context — the external Wikipedia research step, the approximate runtime (~25 seconds), and the quota cost against a daily preview limit. It stops short of saying whether a persistent asset is created or what identifier is returned.

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?

A compact two-clause sentence that front-loads the action (research → generate) before listing outputs and cost. Dense with parentheticals but no filler sentences.

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

Completeness3/5

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

Covers inputs, outputs in prose, and cost, which is decent for a two-parameter generation tool with no output schema. It leaves open what the caller receives (URL, job id, or inline content) and how the daily limit is reported, which matters for a quota-bearing generation call.

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 100%, so both parameters are already documented, and the description only hints at what 'topic' drives (Wikipedia research). No added detail on how 'notes' influences the generated storyboard, so the schema still does the heavy lifting.

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 concrete verb chain and artifact: research a Wikipedia topic and generate an 8–12 shot documentary opening storyboard with narration, Commons images, maps and number cards. The 'preview' framing plus '~25 seconds' implicitly separates it from the full film tool, but no sibling is named explicitly.

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?

Conveys when it fits via 'free' and 'counts toward daily account preview limit', implying a cheap pre-check before committing to a paid full film, but never says to use it instead of / before create_documentary_film or when not to use it.

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.