Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

begin_environment_transaction

Starts a transactional Blender environment session by capturing scene state—objects, meshes, materials, collections, and transforms—to enable atomic rollback of mutations.

Instructions

Begins a transactional environment mutation session backed by UniversalMutationJournal. Captures pre-mutation scene state (objects, meshes, materials, collections, transforms) for atomic rollback.

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

Input Schema

NameRequiredDescriptionDefault
task_idNo
approvedNo
request_idNo
context_nameNoDiagnostic name for the transaction.Environment_Workflow
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It usefully discloses that the session is backed by UniversalMutationJournal and that it snapshots specific scene state (objects, meshes, materials, collections, transforms) for atomic rollback. It omits lifecycle behavior: that the session must eventually be committed or rolled back, whether it locks the scene, and that some parameters suggest an approval gate.

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?

Two sentences, front-loaded with the action and its purpose, with zero filler. The state-capture scope is packed efficiently into a parenthetical.

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

Completeness3/5

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

For a 5-parameter mutation-session tool with no annotations and no output schema, the description covers purpose and snapshot behavior but leaves the transaction lifecycle, approval semantics, and four undocumented parameters unaddressed. An agent would still need to infer how to close the session and what the approval fields require.

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 only 20% (only context_name is documented), leaving task_id, approved, request_id, and approval_token unexplained in the schema. The description supplies no parameter meaning at all, so it fails to compensate for the low coverage on a 5-parameter tool.

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 states a specific verb and resource ('Begins a transactional environment mutation session') and describes the core mechanic (capturing pre-mutation state for atomic rollback). It implicitly distinguishes itself from commit/rollback siblings through 'begins', but does not explicitly name them or state how they pair.

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

Usage Guidelines3/5

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

Usage is implied: you call this to open a transaction before mutating the environment so changes can be rolled back atomically. However, it never states when to use this versus the commit/rollback siblings, nor any prerequisites such as needing approval before beginning a session.

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