Skip to main content
Glama

Check a legacy story and its price

check_legacy_story
Read-onlyIdempotent

Check an AI Legacy Story before it is made, without any charge: the exact price in credits, and (with your own draft) the script as it will be made, cleaned and fitted (keys, voices, scene and shot seconds). Send the same story, draft, references (ids and kinds, no photos needed here), proofCount and options you will send to start_legacy_story. Show the user the script and the price before you start it.

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

Input Schema

NameRequiredDescriptionDefault
draftNoYour own script, in the shape legacy_story_guide shows: title, characters, places, blocks (scenes of shots), proofLines.
modelNoVideo model. Default minimax-h3 (sharpest, keeps each voice).
musicNoMusic bed. Default legacy (dark trap beat, big lift at the end).
storyNoThe story in the user's words (needed when there is no draft)
styleNoLook. Default pixar-3d (3D animated film).
qualityNoSize; must be one the model offers (legacy_story_guide). Default: the model's default (H3: 768p).
secondsNoTarget length of the animated part. Default 60. With your own script, its scenes set the length.
captionsNoBig burned-in captions of the lines. Default big.
languageNoLanguage of the spoken lines. Default en.
proofCountNoHow many real photos the film ends on
referencesNo

Output Schema

NameRequiredDescriptionDefault
draftNo
scenesYes
creditsYes
secondsYes
droppedLinesNo
writerIncludedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, and the description goes beyond them by declaring the call is free of charge and that it returns a computed price rather than starting a job. It also notes references need no photos 'here', implying the check is lighter than the start call. It does not discuss whether the price quote has any validity window or whether draft rendering has limits.

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?

Purpose and free-of-charge fact are front-loaded in the first clause, and the closing imperative is actionable. The middle sentence packing story, draft, references, proofCount and options is dense and slightly run-on, but every element earns its place.

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?

For an 11-parameter tool with nested objects and 91% schema coverage plus an output schema, the description supplies exactly what structured fields cannot: cost behavior, the parity requirement with start_legacy_story, and the show-before-you-start workflow. Return values need not be explained because an output schema exists.

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?

Schema description coverage is 91%, so the schema already carries most parameter meaning; the description still adds value by framing the whole argument set as identical to start_legacy_story's, and by calling out references, proofCount and options as things that must match. The parenthetical 'ids and kinds, no photos needed here' clarifies the references contract beyond the schema's field description.

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?

States a specific verb and resource ('Check an AI Legacy Story before it is made') and enumerates the two outputs: exact price in credits and, when a draft is supplied, the rendered script. It is clearly separable from start_legacy_story, which actually produces the film.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('before it is made', 'before you start it'), an explicit cost condition ('without any charge'), and routes to the sibling by telling the agent to send the same arguments it would send to start_legacy_story. It also adds an operational instruction to show the user the script and price first.

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.

Resources