Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

rollback_environment_transaction

Revert an active Blender environment transaction to its pre-change baseline, restoring objects, collections, meshes, materials, transforms, and parent relationships.

Instructions

Executes compensating rollback for an active environment transaction via UniversalMutationJournal. Restores objects, collections, meshes, materials, transforms, and parents to the pre-transaction baseline.

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

Input Schema

NameRequiredDescriptionDefault
task_idNo
approvedNo
request_idNo
approval_tokenNo
transaction_idNoIdentifier of transaction to roll back (or latest if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 of behavioral disclosure. It usefully states that the tool performs a compensating rollback via UniversalMutationJournal and restores several scene data types to baseline, but it does not disclose approval requirements, permissions, irreversibility, or failure behavior despite parameters suggesting an approval workflow.

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?

The description is two focused sentences with the core action and scope front-loaded. It lists the affected object types efficiently and contains no unnecessary filler.

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 tool with no annotations, no output schema, and five parameters with low schema coverage, the description is incomplete. It should clarify approval requirements, return behavior, and error or state conditions for rolling back an active transaction.

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%, and the description does not explain the meanings of task_id, approved, request_id, or approval_token. It adds little beyond the schema's own description of transaction_id, so it does not compensate for the low coverage.

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

Purpose5/5

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

The description uses a specific verb phrase, 'Executes compensating rollback,' and names the resource, 'active environment transaction.' It also distinguishes the operation from begin/commit behavior by stating that it restores objects, collections, meshes, materials, transforms, and parents to the pre-transaction baseline.

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?

The description clearly implies usage for an active transaction that needs to be rolled back, which gives useful context for when to invoke it. However, it does not explicitly name alternatives such as commit_environment_transaction or state when not to use this tool.

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