Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

execute_environment_workflow

Executes a multi-step environment construction workflow atomically, automatically rolling back to the exact pre-workflow Blender scene state if any step fails.

Instructions

Executes a multi-step environment construction workflow atomically with automatic UniversalMutationJournal rollback if any step fails or encounters an error, restoring the exact pre-workflow scene state.

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": {
      "steps": "<steps>"
    },
    "name": "execute_environment_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYesSequential tool invocation steps.
task_idNo
approvedNo
request_idNo
workflow_nameNoDescriptive name of the multi-tool workflow.EnvironmentWorkflow
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait — atomic execution with UniversalMutationJournal rollback restoring the exact pre-workflow scene state. However, it says nothing about the approval gating implied by the approved/approval_token/request_id parameters, nor about failure modes, side effects outside the scene, or what is returned. For an unannotated multi-mutation tool, that is a significant omission.

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?

A single dense sentence, front-loaded with the verb and the atomicity guarantee, with no filler. It is efficient, though the embedded clause 'or encounters an error' is slightly redundant with 'if any step fails'.

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?

The core mutation-safety story is covered, which is the most important thing for an unannotated write tool, and there is no output schema to explain. But with 6 parameters, 4 of them undocumented and an evident approval workflow that goes unmentioned, an agent cannot fully determine how to invoke it legally.

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 coverage is only 33%, so the description should compensate, and it does not — it never mentions any parameter. The approval-related fields (approved, approval_token, request_id, task_id) are completely undocumented anywhere, and the description does not clarify the sequencing or per-step semantics of 'steps'.

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 names a specific verb and resource ('Executes a multi-step environment construction workflow') and adds the defining trait of atomicity with automatic rollback. It is clearly distinct from single-operation siblings, though it never explicitly contrasts itself with its obvious transaction siblings (begin/commit/rollback_environment_transaction), which is a mild differentiation gap.

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 rather than stated: the reader can infer this is for batch, all-or-nothing multi-tool sequences, but there is no explicit guidance on when to prefer this over the individual transaction siblings or execute_blender_code. No exclusions or prerequisites are given.

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