Skip to main content
Glama

open_blend_file

Load a specified .blend file into Blender so AI clients can inspect, edit, render, or animate the scene.

Instructions

Open a .blend file.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden and delivers none of it. It does not say whether opening replaces the current scene, discards unsaved work, requires an absolute path, or fails on missing files — all critical for a state-replacing operation. This is a significant gap for a mutation-style tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but its brevity comes from omission rather than efficiency. There is no structure beyond a bare restatement, leaving no room for the constraints an agent needs.

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?

An output schema exists, so return values need not be described. However, for a one-parameter file-loading tool that alters editor state, the definition omits everything an agent needs to call it safely: path format expectations and the fate of the currently open file.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the single `path` parameter, but it only implies the value is a .blend file. It gives no guidance on absolute vs relative paths, whether the extension is required, or how path resolution works in the Blender server environment.

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

Purpose2/5

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

"Open a .blend file" essentially restates the tool name (open_blend_file) with no added specificity about what opening entails in this server's context (loading into the current scene, replacing state, etc.). It does not differentiate from the sibling save_blend_file beyond the verb, and the agent learns nothing it could not infer from the name alone.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of preconditions, and no signposting to save_blend_file as the counterpart operation. Nothing tells the agent under what circumstances this should be called.

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

Deploy Server

Other Tools