Skip to main content
Glama

run_operator

Runs an installed Blender operator with structured properties and optional GUI context in a remote session, saving mutations by default for modeling, import/export, and baking tasks.

Instructions

Run an installed Blender operator with structured arguments and optional GUI context.

Use describe_api first. Supports modeling, modes, import/export, baking and more,
as available in this build. EXEC_DEFAULT must report FINISHED. Mutations save by
default. Prefer execute_python for custom logic, data APIs or modal UI interactions.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
contextNoCURRENT
checkpointNo
propertiesNo
session_idYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two meaningful traits: mutations save by default (a side effect) and EXEC_DEFAULT must report FINISHED (a success contract). However, it says nothing about failure/timeout handling, undo or checkpoint behavior, or what 'checkpoint' default=true actually does, leaving significant behavioral gaps for a mutating tool.

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

Conciseness4/5

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

Four short sentences, front-loaded with the purpose, then prerequisite, then scope, then alternative. Little waste, though the 'as available in this build' clause adds ambiguity rather than information.

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?

A 6-parameter mutation tool with no annotations and no output schema needs the description to explain argument passing, context modes, and checkpointing. The description covers only the call sequence and save side effect, leaving the two required and two behaviorally significant optional parameters unexplained.

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% and the description adds almost no meaning: 'structured arguments' loosely gestures at the 'properties' object, and 'optional GUI context' gestures at the 'context' enum, but neither explains expected keys, the CURRENT vs VIEW_3D distinction, or what checkpoint/timeout_seconds control.

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?

States a specific verb and resource: 'Run an installed Blender operator' with 'structured arguments and optional GUI context'. It is distinguishable from execute_python thanks to the explicit routing sentence, though the phrase 'as available in this build' is vague about scope.

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?

Provides an explicit prerequisite ('Use describe_api first') and a clear alternative with the condition that selects it ('Prefer execute_python for custom logic, data APIs or modal UI interactions'). An agent knows both when to use this tool and when to route elsewhere.

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