Skip to main content
Glama

Save or review a season plan

save_season_plan
DestructiveIdempotent

Design, review and confirm the WHOLE season of a series before any episode is made. Free (no credits). A series is fully designed and reviewed before any video is produced, and its characters, voice and style are fixed in every episode. Three steps, one tool: (1) pass plan to save it (version 1: logline, genre, language, narratorVoiceId, styleTokens, characters[] with look, sheetId and wardrobeLock, rules[], at least 3 episodes[] with title, characterName, cliffhangerLine and shots[] or a script). Every edit clears the review and the confirmation. (2) pass review: true (with or without plan) to run the season review: a deterministic checklist (cliffhangers, hooks, one narrator and style, no on-screen text, one subject per look and per shot, outfit locked, season price) plus an advisory AI review that lists up to 8 concrete issues; if the AI review cannot run the answer says so and the checklist stands. (3) show the human the checklist, the AI issues and the season price, and ONLY after they say yes call again with confirm: true and planHash from the review. Every character an episode uses needs a READY sheet of this series (create_character_sheet, one sheet per character) whose id is in the plan. Then quote_character_episode / create_character_episode make the planned episodes. Characters are fictional adults (or animals / mascots), AI-generated: no real or famous people, no children or anyone who looks under 18, no sexual content, no logos or protected characters (refused with CONTENT_POLICY, nothing charged). Everything made here is AI-generated and labelled as such. Requires the "video:create" 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": "save_season_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoThe whole season plan. Omit to review or confirm the stored one.
reviewNoRun the season review on the stored plan (after saving `plan` if given).
confirmNoThe owner confirms the reviewed plan. Needs planHash; do not send `plan` in the same call.
aiReviewNoWith review: also run the advisory AI review (default true).
planHashNoWith confirm: the planHash the review returned.
seriesIdYesA series id from list_series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that the call is free, that every edit clears the review and confirmation, that a missing AI review merely degrades to the checklist, that confirm needs a planHash and cannot be combined with `plan`, that a READY character sheet is required, and that policy violations return CONTENT_POLICY with nothing charged plus a video:create scope requirement. Only the destructiveHint=true is not fully explained in terms of what exactly gets overwritten.

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 purpose and cost in the first sentence, then organizes the three modes as a numbered list, which suits the branching behavior. It is long, and the content-policy paragraph is dense, but nearly every sentence carries information an agent needs before calling.

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 still signals return values (planHash from the review, the checklist, up to 8 AI issues, the season price) and explains fallbacks. For a 6-parameter, deeply nested tool this is complete enough to invoke correctly.

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 schema already carries field-level meaning, but the description still adds workflow-level semantics the schema cannot express: plan vs review vs confirm exclusivity, aiReview defaulting to true, and that planHash comes from the review response.

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 set (design, review, confirm) and a precise resource (the whole season of a series), and frames the scope 'before any episode is made', which cleanly separates it from the per-episode siblings like create_character_episode.

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 three-step workflow with conditions: pass `plan` to save, `review: true` to evaluate, `confirm: true` only after the human says yes, and it names the downstream tools (create_character_sheet, quote_character_episode, create_character_episode) that handle the next phase. The only minor omission is that it never names the sibling for simply reading a stored plan, though 'omit plan to review the stored one' partially covers that.

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