Skip to main content
Glama

save_project

Queue a durable Blender session checkpoint for recovery, and optionally export the current workspace as a downloadable .blend by providing a new path.

Instructions

Queue a durable checkpoint. Optional new workspace path exports a .blend for download.

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": {
      "session_id": "<session_id>"
    },
    "name": "save_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses little beyond the async nature implied by 'queue'. It omits whether prior checkpoints are overwritten, permissions needed, how long the operation takes, and whether a job_status poll is required to learn the outcome.

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?

Two sentences, front-loaded with the verb, no filler words. However, the first is under-specified rather than concise, and the second conflates an optional parameter with a downloadable artifact, requiring the reader to unpack it.

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

Completeness2/5

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

For a mutation-like tool with no annotations, no output schema, and 0% schema coverage, the description leaves key questions open: where the checkpoint is stored, whether repeat calls are safe, and what signals success. Insufficient for an agent to invoke confidently.

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?

Schema coverage is 0%, so the description must define both parameters. It meaningfully explains path (new workspace path triggers a .blend export for download), which is genuinely useful. However, session_id – the only required parameter – is never mentioned, leaving a gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action ('Queue a durable checkpoint') but the resource is vaguely characterized – 'checkpoint' is named yet what is captured (session state? project state?) is only implied by the tool name. The .blend export mention hints at scope, but a reading agent must infer what a checkpoint contains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus restore_checkpoint or list_checkpoints. The only conditional content is 'Optional new workspace path exports a .blend,' which is parameter behavior, not usage guidance. No prerequisites or exclusions given.

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