Skip to main content
Glama

Get a season plan

get_season_plan
Read-onlyIdempotent

Read the season plan of one of your series: the plan (logline, genre, narrator voice, language, style, cast with outfits, every episode), its hash, its status (none, saved, reviewed or confirmed) and the recorded season review (a checklist with pass or fail per rule, the season price and, if it ran, the AI review). Free. An episode can only be made from a plan that is reviewed and confirmed: use this to see where the plan stands and which episodes can be quoted. 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": "get_season_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesA series id from list_series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly, idempotent, closed-world) by disclosing that the call is free, which OAuth scope is required ("video:read"), the exact status vocabulary (none, saved, reviewed or confirmed), and the structure of the recorded season review including the checklist, season price and optional AI review.

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 the core action and keeps everything in three sentences with no filler; each clause carries information (contents, status, review, gate for quoting, scope). The long parenthetical inventory is dense but justified since there is no output schema to lean on.

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 must convey return values and it does so thoroughly — plan fields, hash, status enum, and review contents. It also covers cost and authorization, leaving nothing an agent needs before calling it.

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% and the single seriesId parameter is fully documented as 'A series id from list_series'. The description adds the framing 'of one of your series' but no new format, constraint or meaning beyond the schema, so the baseline 3 applies.

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 ('Read the season plan') and immediately enumerates what the plan contains (logline, genre, narrator voice, language, style, cast with outfits, every episode), plus hash, status and review. An agent can distinguish this read tool from siblings such as save_season_plan or plan_drama_season without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear usage context: 'use this to see where the plan stands and which episodes can be quoted', reinforced by the rule that an episode can only be made from a reviewed and confirmed plan. It does not name a competing tool or state an explicit when-not-to-use case, so it stops short of a 5.

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