Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_building_envelope

Builds a complete exterior building envelope with foundation slab, facade walls, floor slabs, doorway apertures, and integrated roof geometry for architectural modeling in Blender.

Instructions

Constructs a complete exterior building envelope with structural foundation slab, exterior facade walls, multi-story floor slabs, structured doorway apertures, and seamlessly integrated roof structure.

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_building_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the building envelope object.BuildingEnvelope
widthNoBuilding envelope width along X axis in meters.
heightNoTotal wall/facade height in meters.
lengthNoBuilding envelope length along Y axis in meters.
storiesNoNumber of stories/floors in building.
task_idNo
approvedNo
locationNo
door_wallNoWall containing primary entrance aperture.SOUTH
roof_typeNoIntegrated roof geometry type.GABLE
door_widthNoEntrance doorway width in meters.
request_idNo
door_heightNoEntrance doorway height in meters.
roof_heightNoRise of integrated roof in meters.
roof_overhangNoEaves overhang beyond exterior walls in meters.
approval_tokenNo
wall_thicknessNoExterior facade wall thickness in meters.
foundation_thicknessNoFoundation slab thickness in meters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a compound creation producing multiple components (foundation, walls, slabs, apertures, roof), which is genuinely useful context, but says nothing about whether existing geometry is replaced, whether scene state changes destructively, or what permissions apply. The presence of unexplained governance parameters (approved, approval_token, task_id, request_id) suggests a gated workflow that the description does not mention at all.

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?

One front-loaded sentence with the verb first and a clean enumeration of outputs; every phrase carries information. It is slightly long and could lose an adjective ('complete', 'seamlessly integrated') without loss, but there is no padding or repetition.

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 an 18-parameter compound-creation tool with no annotations and no output schema, the description is thin. Nothing explains the approval/task parameters, whether the result is one joined object or a hierarchy of objects, or what the tool returns to the caller. The absence of an output schema means the description should say something about the resulting scene structure, and it does not.

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 72%, so most parameters are self-documented and the baseline of 3 applies. However, the 28% that are undocumented in the schema are exactly the consequential ones (approved, approval_token, task_id, request_id), and the description adds no meaning for any parameter — it only loosely implies that door_* maps to 'doorway apertures' and roof_* to the roof. It does not compensate where compensation is needed.

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?

Names a specific verb ('constructs') and a specific composite resource ('complete exterior building envelope'), then enumerates the parts produced: foundation slab, facade walls, floor slabs, doorway apertures, roof. An agent knows exactly what geometry results. It stops short of differentiating from siblings like create_roof_structure or create_room_enclosure, which also build structural geometry.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing. The word 'complete' implies this is the all-in-one option versus piecemeal creation via create_roof_structure or create_room_enclosure, but the agent must infer that. No prerequisites or ordering guidance is 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