Skip to main content
Glama

Run assessment and breakdown

run_breakdown
Destructive

Runs the Aufilm assessment and scene-by-scene breakdown on the production's screenplay and builds the plan: the breakdown in 14 tagged categories, the shooting schedule (the stripboard the first assistant director works from) and the Day Out of Days, plus the editable budget — and the financing plan and festival matches where the production is unlocked. Returns a summary of the finished plan, including any warnings about the screenplay's formatting. Call it after create_project with script_text, and again to rebuild the plan when the screenplay changes.

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": "run_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
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/replace nature is known. The description adds real context — what gets built, that the financing plan and festival matches only appear 'where the production is unlocked', and that the return is a summary with screenplay-formatting warnings. However, given destructiveHint=true it never says that re-running replaces an existing plan (and any prior budget edits), which is the single most consequential behavior an agent needs to know before rebuilding.

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?

Information is front-loaded: verb and outputs first, invocation guidance last. The output enumeration is dense but each item is a distinct artifact the agent needs to know about. The stray 'with script_text' clause is the one piece of wording that does not earn its place.

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

Completeness3/5

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

An output schema exists, and the description still usefully signals that the response is a summary with formatting warnings. For a complex, destructive plan-generation tool, though, it omits the effect of re-running on existing plans and the 'unlocked' gating condition is mentioned without saying how the agent should act on it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter project_id has zero schema description coverage, and the description does not explain it at all. Worse, it says to call 'with script_text' even though no script_text parameter exists on this tool, which can send an agent looking for an argument that isn't in 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?

Uses a specific verb (runs the assessment and breakdown) on a specific resource (the production's screenplay) and enumerates exactly what artifacts are produced: 14-category breakdown, stripboard schedule, Day Out of Days, editable budget, financing plan and festival matches. It is clearly distinguishable from read-side siblings such as get_breakdown, get_schedule, and get_budget.

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?

Explicitly states the ordering and trigger: 'Call it after create_project with script_text, and again to rebuild the plan when the screenplay changes.' That covers when to call and when to re-call. It stops short of stating when not to call (e.g., use get_breakdown to simply read an existing plan without regenerating), so it falls just shy 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