Skip to main content
Glama

open_project

Replaces the live Blender scene with an uploaded .blend file and disables embedded script auto-run; save edits first, since a successful open creates a new checkpoint.

Instructions

Replace the live scene with an uploaded .blend; disables embedded script auto-run.

Save current edits first. Successful open creates a new checkpoint.

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>",
      "path": "<path>"
    },
    "name": "open_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral load. It does well on the destructive side: it replaces the live scene, warns that the caller should save first, disables auto-run of embedded scripts (a security trait no annotation would have declared), and notes that a checkpoint is created, so the change is recoverable. It says nothing about failure modes, what happens to session state, or the upload prerequisite in 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?

Three short sentences, each earning its place. The destructive replacement leads, the safety caveat and the checkpoint side effect follow. There is zero filler.

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?

For a two-parameter mutation tool with no output schema and no annotations, it covers the destructive scope, the saving prerequisite, the security behavior, and the checkpoint side effect. Only the meaning of session_id and the expected errors are missing.

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 description coverage is 0%, so the schema documents neither parameter. The description implies that 'path' refers to a previously uploaded .blend, which is real added meaning. It says nothing about 'session_id', though, which leaves an undocumented parameter.

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 gives a specific verb and resource: 'Replace the live scene with an uploaded .blend'. That is clearly distinct from save_project and restore_checkpoint. It never names a sibling, so it stops short of the top mark for differentiation, but an agent can still tell what the tool does.

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

Usage Guidelines4/5

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

'Save current edits first' warns of a precondition and points implicitly to save_project. That gives a clear usage context, but the description never explicitly contrasts this tool with restore_checkpoint or explains when to prefer restoring over opening.

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