Skip to main content
Glama

Quote a character episode

quote_character_episode
Read-onlyIdempotent

Price one PLANNED episode (12-60 seconds, 3-8 shots) of a series with a confirmed season plan, starring the character the plan names. FREE: it spends nothing and starts nothing. Returns the shot plan (narration, action, camera and seconds of every shot), the exact credits (up to 313 credits for a default 12-second episode; longer ones (up to 60 seconds) cost more: an AI clip per shot, a still per shot and the narration), and a ready-made nextAction for create_character_episode. Show the human the price and the shots, and call the create tool only after they say yes. The same safety checks as the real call run here: real or famous people, anyone who looks under 18, sexual content and protected characters are refused with CONTENT_POLICY. Only an episode of a REVIEWED, CONFIRMED season plan can be quoted or made: send its script or shots exactly as planned (get_season_plan). Without a confirmed plan the answer is SEASON_PLAN_REQUIRED or SEASON_NOT_REVIEWED, and for shots that are not a planned episode EPISODE_NOT_IN_PLAN, each with a nextAction. The narrator voice, the language, the style and the character come from the plan and cannot be overridden (SEASON_FIELD_LOCKED); to change an episode, edit the plan (that clears the review). Requires the "video:read" scope.

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": {
      "seriesId": "<seriesId>"
    },
    "name": "quote_character_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotsNoThe shots of the planned episode. Give `shots` OR `script`.
titleNoOptional title.
scriptNoThe narration, about 29-147 words. The system splits it into shots by sentence. Give `script` OR `shots`, exactly as planned (get_season_plan).
sheetIdNoOmit it: the character sheet is the one the season plan names for this episode. If given it must equal that sheet.
languageNoOmit it: the narration language is the season plan's. If given it must equal the plan's.
seriesIdYesA series id from list_series whose season plan is reviewed and confirmed.
shotCountNoWith `script`: how many shots to split it into. Omit for an automatic count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / script / description
      Previous value: -"The narration, about 74-147 words. The system splits it into shots by sentence. Give `script` OR `shots`, exactly as planned (get_season_plan)."New value: +"The narration, about 29-147 words. The system splits it into shots by sentence. Give `script` OR `shots`, exactly as planned (get_season_plan)."
    • changedInput schema / properties / script / minLength
      Previous value: -120New value: +60
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/idempotent/non-destructive; the description goes far beyond by confirming nothing is spent or started, that the same CONTENT_POLICY safety checks run, and by naming the failure codes (SEASON_PLAN_REQUIRED, SEASON_NOT_REVIEWED, EPISODE_NOT_IN_PLAN, SEASON_FIELD_LOCKED) each with a nextAction. It also discloses the required video:read scope and the plan-locked fields that cannot be overridden.

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?

The cost and the free-preview nature are front-loaded, followed by the return value, the approval workflow, and then the error conditions in a logical order. It is a single dense block, though, and the error-code enumeration could be tightened or bulleted for faster scanning.

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 no output schema, the description carries the return-value burden and does so: shot plan contents (narration, action, camera, seconds), exact credit cost with a concrete ceiling, and a ready-made nextAction for the create tool. Prerequisites, scope requirements, and all rejection paths are covered for a 7-parameter tool.

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 coverage is 100%, so the baseline is 3, and the description earns an extra point by stressing that shots or script must be sent exactly as planned and that sheetId, language, narrator, style and character are inherited from the plan and rejected if they differ. It adds constraint meaning rather than restating field text.

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: price (quote) one PLANNED episode of a series, with concrete scope bounds (12-60 seconds, 3-8 shots) and the precondition that the character comes from a confirmed season plan. It is clearly distinguishable from create_character_episode, which it names as the follow-up action.

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?

Explicitly says this is a free preview, that the human must be shown the price and shots, and that create_character_episode should only be called after approval. It also states the prerequisite (a REVIEWED, CONFIRMED season plan via get_season_plan) and the alternative path when that is missing.

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