Skip to main content
Glama

get_project

Read-onlyIdempotent

Reads a compact, read-only overview of the whole project—scenes, shots, IDs, camera, cast, actions, texts, and transitions—so you can get the IDs required before editing.

Instructions

Read-only: the whole project in short form. Style, format, and every scene and shot with id, index, length, camera, place, cast (member ids and refs), number of actions, texts and transition. Read it before editing to get the ids other tools need. For every setting of one shot use get_shot; for a picture use look.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds value beyond them by characterizing the payload as a 'short form' summary (deliberately lossy, with detail deferred to get_shot) and by stating the workflow role of the result: supplying ids other tools require. It does not mention size limits or response envelope, which keeps it from 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?

Front-loaded with the read-only scope, then a dense field listing, then the workflow rule and alternatives. Four sentences, each carrying information, though the long comma-separated field enumeration is heavy and could be trimmed without losing routing value.

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

Completeness5/5

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

There is no output schema, so the description must describe returns — it does, enumerating the top-level fields and explicitly flagging that shots carry ids, indices, camera, place, cast, action counts, texts and transition. Combined with the alternatives (get_shot, look) and the no-parameter schema, an agent has everything needed to call it correctly.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to supply; per the zero-param baseline this is a 4. The description correctly implies the tool is invoked with no arguments, focusing instead on the return contents.

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 plus scope: 'Read-only: the whole project in short form', then enumerates exactly what short form contains (style, format, scenes and shots with ids, indices, camera, place, cast, actions, texts, transition). It also explicitly distinguishes itself from get_shot (one shot's settings) and look (a picture), so an agent can separate it from siblings without opening a schema.

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 when-to-use rule ('Read it before editing to get the ids other tools need') and names the alternatives with the conditions that select them ('For every setting of one shot use get_shot; for a picture use look'). This is when/when-not plus alternatives, not inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.