Skip to main content
Glama

How to write a legacy story

legacy_story_guide
Read-onlyIdempotent

AI Legacy Story: a short vertical film in a 3D animated (Pixar-like) style that tells a real life or business story only through on-screen dialogue (no narrator), with lip-synced voices, captions, music and the person's real photos at the end. This returns the options (models, sizes with prices, music, styles, voices, languages, limits) and the exact rules and JSON shape of a script. Use it when the user wants their story, their company's story or a family member's life as an animated film. You can then write the whole script yourself (any model, in the user's own way) and pass it to check_legacy_story and start_legacy_story as draft; then MakeViral does not write it and does not charge for writing it. Without a script, start_legacy_story writes it from the story text.

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

Input Schema

NameRequiredDescriptionDefault
modelNoVideo model. Default minimax-h3 (sharpest, keeps each voice).
musicNoMusic bed. Default legacy (dark trap beat, big lift at the end).
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 (the script then has that many proofLines)
referencesNoThe photos the user will send (ids, kinds, names), so the rules list them

Output Schema

NameRequiredDescriptionDefault
guideYes
choicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description is consistent with a pure reference lookup. It adds real context beyond the annotations: this call itself produces no film, and supplying your own `draft` means MakeViral neither writes nor charges for the script. It does not discuss caching or rate limits, but nothing contradicts the declared safety profile.

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-loaded with the product definition, then the return payload, then usage and the script/draft workflow, so the agent gets the essentials first. It is dense with parentheticals and long clauses, but nearly every sentence carries decision-relevant information. Slight trimming of the style adjectives would help.

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 9 optional parameters, an output schema and strong annotations, the definition covers what an agent still needs: what the tool returns, when to call it, and how it hands off to the check/start siblings. Nothing needed to call it correctly is missing.

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 every parameter, enum and default is already documented in the schema; the description only adds the meta-point that the valid model/size combinations come from this guide. It does not elaborate on the reference/proofCount interplay beyond what the schema already states. Baseline 3 is appropriate when the schema carries the parameter burden.

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 deliverable: it returns the options (models, sizes with prices, music, styles, voices, languages, limits) plus the exact rules and JSON shape of a legacy-story script. It also defines what a legacy story is (vertical 3D-animated film, dialogue-only, lip-synced, real photos at the end), which no sibling name conveys. An agent can distinguish it from check_legacy_story and start_legacy_story purely from this text.

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 trigger ("Use it when the user wants their story, their company's story or a family member's life as an animated film") and routes the downstream flow: write the script yourself and pass it as `draft` to check_legacy_story and start_legacy_story, otherwise start_legacy_story writes it from the story text. It even explains the incentive for doing so (no writing charge), which is exactly the decision an agent needs to make.

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