Skip to main content
Glama

Production summary

get_project
Read-only

Summary of one production: planning status, scene and shoot-day counts, what has been generated and the production's access state. The budget total is included for the free first production and for unlocked productions. Use it to check where a production stands before reading or re-running its plan.

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

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description isn't burdened there. It adds genuinely useful behavioral context: the budget total is conditionally present, only for the free first production and unlocked productions, which tells the agent to expect partly-gated data rather than a complete record.

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

Conciseness5/5

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

Two sentences with no filler; the payload summary is front-loaded and the access-state caveat about budget totals is placed where it is most needed. Every clause carries information.

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 an output schema available, the description need not enumerate return fields, and it appropriately focuses on scope and the conditional budget disclosure. It is close to complete for a single-parameter read tool; only the identifier format and not-found behavior are left unstated.

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 with 0% schema description coverage, so the schema contributes only a name ('project_id') and type. The description implies a single production is targeted, but it does not clarify identifier format, whether it accepts a slug or numeric ID, or what happens for an unknown ID.

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 ('Summary of one production') and enumerates its contents: planning status, scene and shoot-day counts, generated artifacts, and access state. This is far more than a restatement of the name. It does not, however, distinguish itself from siblings such as get_budget or get_breakdown, which overlap on the budget/scene data it mentions.

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 use context: 'check where a production stands before reading or re-running its plan,' which implies an orienting/overview role. But there is no explicit when-not-to-use or named alternative, so an agent must infer that get_budget or get_breakdown are the deeper-dive tools.

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