Skip to main content
Glama

Financing plan

get_financing_plan

The financing plan of the production: funding layers, the equity gap, routes by locality, the incentives and grants that fit it, the funding watch list and, where built, the detailed plan — the financing preparation a producer or director takes into a raise. Use it when the user asks how the film can be financed or which grants, funds and incentives fit it. Part of the production's unlock (Production or Producer's Desk for this production, or the Studio slate plan); on a production without it, the tool returns exactly what the unlock opens.

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

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real behavioral context beyond the annotations: the result is scoped to the production's 'unlock', and on a production without that unlock it returns only what the unlock opens (i.e. a partial/empty payload). That is useful gating information the annotations do not convey. However, annotations declare readOnlyHint=false, and the description never states whether invoking this can create or mutate the plan/unlock, leaving a genuine ambiguity for a non-read-only tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a dense em-dash list of deliverables that is front-loaded and informative, but it is long and reads as inventory rather than guidance. The trailing 'unlock' sentence is jargon-heavy and costs more attention than the value it returns; the definition could be materially tighter.

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, so return values need not be explained, and the description does cover what the payload contains. What is missing is clarification of the 'unlock' concept and whether calling the tool has side effects, which matters given readOnlyHint=false. For a single-parameter read-style tool it is adequate but leaves the one non-obvious mechanic unexplained.

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?

There is one parameter (project_id) at 0% schema description coverage, so the description must carry the load. It refers to 'the production' and 'for this production', which implies the parameter scopes to a single production, but it never names or describes project_id's expected value or format.

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 concrete resource and enumerates its contents (funding layers, equity gap, routes by locality, incentives and grants, funding watch list, detailed plan), which is far more specific than the title alone and distinguishes it from get_budget-style siblings. It stops short of naming an adjacent tool it should not be confused with, so it is clear but not sibling-differentiated.

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?

It gives an explicit trigger: 'Use it when the user asks how the film can be financed or which grants, funds and incentives fit it.' That is a clear positive condition. There is no when-not guidance or named alternative (e.g. versus get_budget for cost-side questions), which keeps it below 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