Skip to main content
Glama

Scene breakdown

get_breakdown
Read-only

The scene-by-scene breakdown of the production: scene headings, page eighths, synopsis and the elements tagged in each of the 14 breakdown categories (cast, background, props, wardrobe, set dressing, vehicles, stunts, effects and more) — the breakdown a producer, director or assistant director works from in pre-production. Use it when the user asks what is in a scene or which elements the production needs.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the exact shape of the returned content (headings, eighths, synopsis, 14 element categories) and the pre-production workflow it serves. It says nothing about result size or pagination for a potentially large scene list, which keeps it off a 5.

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 purpose is front-loaded and the use case trails it, which is the right order. The parenthetical category list is long and tails off into 'and more', which is slightly padded, but most of the wording carries genuine information about what is returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only one required parameter and an output schema present, the description does not need to document return values or field formats and is complete enough to invoke correctly. Its only real omission relative to the sibling set is any signal about how it differs from 'run_breakdown'.

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 0%, so the schema contributes only the name 'project_id'. The description never mentions the parameter at all — it is only passingly inferable from 'the production'. With a single, intuitively named required parameter the gap is small, but the description adds no meaning the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (scene-by-scene breakdown of the production) and enumerates its contents: scene headings, page eighths, synopsis, and the 14 tagged element categories. That is far more than a restatement of the name, but it never distinguishes this from the sibling 'run_breakdown', so an agent cannot tell which of the two to pick from the description alone.

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

Usage Guidelines3/5

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

It gives a usable trigger — 'use it when the user asks what is in a scene or which elements the production needs' — which is clear positive guidance. It offers no exclusions or comparison to alternatives, and the closely named sibling 'run_breakdown' is left unaddressed, so the when-not condition has to be inferred.

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