Skip to main content
Glama

Budget

get_budget
Read-only

The production budget Aufilm builds from the breakdown: section subtotals, line items and the grand total in the production's currency — the budgeting document a producer takes to financiers. Use it for a production that already exists in Aufilm and has been planned (run_breakdown has run on it): when the user asks what that film will cost or wants its budget estimate, read this instead of estimating from the screenplay yourself. For a screenplay that is not a production yet, call create_project first, then run_breakdown, then this. The budget of the account's first production is free and editable in the conversation: present its lines, and revise amounts with the user in the chat. Professional budget exports (top sheet PDF, the Saturation bundle) belong to the production's unlock.

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_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful non-obvious context: the prerequisite that the breakdown must have run, and the monetization boundary (first production's budget is free and conversationally editable; top-sheet PDF and Saturation exports require the production's unlock). It does not describe pagination or freshness of the figures, but with annotations carrying the safety profile this is solid added value.

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-loaded with the resource and its contents, then conditions, then the fallback chain, then monetization caveats — a logical order with no filler. It is dense and long for a single-parameter read tool, and the financier framing in the opening sentence is decorative rather than actionable.

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?

An output schema exists, so return values need not be explained, and the description covers prerequisites, routing, and the export boundary that an agent must not over-promise. The only gap is that it never names project_id explicitly, leaving the parameter-to-production mapping implicit.

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

Parameters5/5

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

Schema coverage is 0% for the single project_id parameter, so the description must carry the meaning — and it does, tying the call to 'a production that already exists in Aufilm' and describing the prerequisite state that makes the id valid. That gives an agent enough to know which id to pass and when the call will succeed.

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: it returns the production budget Aufilm builds from the breakdown, and enumerates the contents (section subtotals, line items, grand total, currency). The opening clause about 'the budgeting document a producer takes to financiers' makes it clearly distinct from get_breakdown and create_export.

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 use condition (production exists in Aufilm and run_breakdown has run on it) and an explicit counter-case with an ordered fallback chain: for a screenplay that is not yet a production, call create_project, then run_breakdown, then this. It also rules out the competing behavior of estimating cost from the screenplay manually.

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