Skip to main content
Glama

save_project

Saves the open animated video project to a .dino file, optionally as a new file by name or path, and returns the saved file path.

Instructions

Save the open project to a .dino file, the same as File > Save. With path: Save As to that file. With name: a new file with that name in the person's projects folder. A project never saved before gets a file in the projects folder. Returns the file path. To save it as a reusable starting point, use templates with save.

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

Input Schema

NameRequiredDescriptionDefault
nameNoA name for a new file in the projects folder.
pathNoFull path ending in .dino.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare write/idempotency flags; the description adds what the agent actually needs — that a never-saved project still gets a file in the projects folder, that the call returns the file path, and the exact Save As semantics. The remaining gap, behavior when the given path already exists, is minor for a save tool.

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 short sentences, front-loaded with the core action, then the two argument modes, then the default case and return value. There is no filler and each clause carries distinct 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?

No output schema exists, and the description compensates by stating that the file path is returned. For a 2-parameter mutation tool this is close to complete; only conflict handling between name and path and failure modes are unstated.

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% so the baseline is 3, but the description adds real meaning on top of the schema: path carries Save As semantics while name targets the projects folder. It does not say what happens if both name and path are supplied, which is the one ambiguity left.

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 ("Save the open project to a .dino file") and anchors it to the familiar File > Save behavior. It also separates the Save vs Save As vs never-saved cases, which makes it clearly distinct from open_project, new_project, and get_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 conditional usage: no argument = plain save, path = Save As, name = new file in the projects folder. It also routes one adjacent need elsewhere by naming templates plus save for saving a reusable starting point, so the agent does not have to guess an alternative.

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