Skip to main content
Glama

new_project

Destructive

Create a new empty animated video project by replacing the open project with one scene and shot; choose style/format, confirm the reset, and undo afterward if needed.

Instructions

Replace the open project with a new, empty one (one scene, one shot with the style's start place, light and lead character). The first call only says what will happen; ask the person, then call again with confirm: true. The person can Undo it right after. To keep the project and only change its look, use set_style; to open a saved file, use open_project. Returns the new scene and shot ids.

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": "new_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoStyle id from list_styles, like pixel, toon, voxel, docu. Left out: the current style.
formatNohorizontal 16:9 or vertical 9:16. Left out: the current format.
confirmNotrue only after the person said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / style / description
      Previous value: -"Style id, like pixel, toon, voxel, docu. Left out: the current style."New value: +"Style id from list_styles, like pixel, toon, voxel, docu. Left out: the current style."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the destructive nature is known, but the description adds genuinely useful context: the entire open project is replaced, what is created in its place, that the person can Undo afterwards, and that a confirm round-trip is mandatory. A 3 reflects that it largely reinforces the annotation rather than adding substantial new behavioral detail.

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?

Four tight sentences, front-loaded with what the tool does and what it produces, followed by the interaction protocol and alternatives. Every clause earns its place, including the return-value note, which is needed because there is no output schema.

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?

Covers the mutation's scope, the consent protocol, recoverability via Undo, sibling alternatives, and the return values, so nothing an agent needs in order to invoke this destructive tool safely is missing. Its lack of an output schema is compensated for by 'Returns the new scene and shot ids'.

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?

Schema coverage is 100% and every parameter is already documented, so the baseline is 3. The description adds meaning beyond the schema by explaining that 'confirm' represents the second call in a two-step consent protocol ('The first call only says what will happen'), not just a boolean flag.

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 the specific verb 'replace' on a specific resource ('the open project') and then enumerates exactly what the new project contains (one scene, one shot with the style's start place, light and lead character). It also explicitly distinguishes itself from the sibling tools that could be confused with it (set_style, open_project).

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 explicit routing rules: keep the project and only change the look → set_style; open a saved file → open_project; otherwise this tool. It also spells out the required two-step interaction ('The first call only says what will happen; ask the person, then call again with confirm: true'), so an agent cannot invoke it the wrong way.

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