Skip to main content
Glama

Read a season plan

autoshort_get_season_plan
Read-onlyIdempotent

Retrieve a series' season plan, hash, status, and review checklist to check plan readiness and which episodes can be quoted.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
seriesIdYesA series id from autoshort_list_series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it is free (no credit cost), it discloses the status vocabulary (none, saved, reviewed, confirmed) and the business rule that only reviewed-and-confirmed plans can yield episodes, including whether the season price and AI review are present.

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 action and resource, then the return payload, then the cost note, then the usage rule — a sensible order. The parenthetical inventory is dense and slightly run-on, but every element (payload fields, status values, 'Free', quoting precondition) carries information an agent needs.

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?

There is no output schema, and the description compensates fully by describing the returned plan fields, hash, status enumeration and review contents. For a single-parameter read tool this leaves no material gap an agent would need 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?

Only one parameter exists and schema coverage is 100%; the schema itself states seriesId comes from autoshort_list_series. The description's 'of one of your series' merely restates that, adding no format, constraint or lookup guidance beyond the schema.

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?

Opens with a specific verb+resource ('Read the season plan of one of your series') and then enumerates exactly what the payload contains: logline, genre, narrator voice, cast with outfits, episodes, hash, status and review. An agent can distinguish this read tool from the write-side siblings like autoshort_save_season_plan or autoshort_plan_drama_season without opening a 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 concrete decision context: use it to see where the plan stands and which episodes can be quoted, backed by the rule that an episode can only be made from a reviewed-and-confirmed plan. It lacks an explicit when-not or a named alternative for creating/saving plans, so it falls just short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.