Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_room_enclosure

Builds solid manifold room enclosures in Blender with configurable dimensions, wall thickness, floor and optional ceiling slabs, plus doorway and roof options.

Instructions

Creates a solid manifold architectural room enclosure with parameterized width, length, wall height, wall thickness, floor slab, optional ceiling slab, and structured doorway apertures.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the room enclosure object.InteriorRoom
widthNoInterior room width along X axis in meters.
heightNoInterior room height along Z axis in meters.
lengthNoInterior room length along Y axis in meters.
task_idNo
approvedNo
locationNo
door_wallNoWall containing doorway cutout (or 'NONE').NONE
roof_typeNoOptional integrated roof structure type atop the room walls.NONE
door_widthNoDoorway aperture width in meters.
request_idNo
door_heightNoDoorway aperture height in meters.
door_offsetNoOffset from wall center along wall axis in meters.
roof_heightNoRise of the integrated roof in meters.
include_floorNoWhether to generate floor slab.
roof_overhangNoOverhang of the integrated roof beyond walls.
approval_tokenNo
wall_thicknessNoWall thickness in meters.
include_ceilingNoWhether to generate ceiling slab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 behavioral burden. It usefully discloses that the result is a solid manifold enclosure with optional ceiling and doorway apertures, but it does not explain mutation side effects, approval requirements, or what happens when approval fields are omitted.

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?

The description is a single front-loaded sentence with no filler. It is dense but readable, though its long run-on structure could be split for easier scanning.

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?

This is a complex 19-parameter creation tool with no annotations and no output schema. The one-sentence description does not cover usage guidance, approval behavior, return effects, or relationship to sibling creation tools, leaving important context missing.

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

Parameters3/5

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

Schema coverage is 74%, so most geometry parameters are already documented in the schema. The description groups width, length, wall height, wall thickness, floor slab, ceiling slab, and doorway apertures, but it adds little meaning for roof-related parameters or the undocumented task_id, approved, location, request_id, and approval_token fields.

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 uses a specific verb, 'Creates', and a specific resource, 'room enclosure', and enumerates key geometric features. It does not explicitly distinguish the tool from siblings such as create_building_envelope or create_roof_structure, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no when-not-to-use exclusions, and no alternatives to this tool. It also does not explain prerequisites or the approval workflow implied by the approved/approval_token parameters.

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