Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_roof_structure

Generates parametric watertight solid roof structures (gable, hip, pitched, shed, flat) with adjustable span, rise, thickness, overhang, and optional snapping to existing buildings.

Instructions

Generates a parametric watertight solid roof structure ('GABLE', 'HIP', 'PITCHED', 'SHED', 'FLAT') with specified span, rise height, rafter/slab thickness, eaves overhang, and optional snapping to existing building objects.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the roof object to create.ArchitecturalRoof
solidNoWhether to generate closed watertight manifold solid geometry.
widthNoBase roof span along X axis in meters.
heightNoRidge rise height above base elevation in meters.
lengthNoBase roof length along Y axis in meters.
task_idNo
approvedNo
locationNo
overhangNoEaves overhang beyond footprint in meters.
roof_typeNoRoof architecture geometry type.GABLE
thicknessNoRoof slab or rafter thickness in meters.
request_idNo
approval_tokenNo
base_elevationNoBase elevation Z coordinate where the roof rests.
target_buildingNoOptional name of building/enclosure object to automatically snap and match dimensions to.

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 supplied, so the description carries the full behavioral burden. It discloses that geometry is watertight/manifold, but says nothing about the approval workflow implied by approved/approval_token/task_id/request_id, whether it mutates or snaps to the target building, or what happens on failure.

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 that front-loads the core action and enumerates the key geometry inputs without filler. It is efficient, though the parenthetical type list makes it slightly list-heavy.

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 15-parameter creation tool with no annotations and no output schema, the description covers the geometric essentials but omits the approval/task parameters and any statement of return value or side effects. Adequate but with clear gaps.

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 67%, and the description usefully maps several parameters to plain language (span, rise height, rafter/slab thickness, eaves overhang, snapping target). However, it leaves the approval/transaction parameters and base_elevation/location unexplained, so it only partially compensates for the coverage gap.

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?

States a specific verb ('Generates') and a precise resource ('parametric watertight solid roof structure'), and enumerates the supported roof types and geometric inputs. It is clearly a roof-construction tool, though it does not explicitly contrast itself with siblings like create_building_envelope or create_room_enclosure.

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 prerequisites, and no alternatives. The only contextual hint is that snapping to an existing building object is optional, which implies a workflow but does not tell the agent when to prefer this tool over the envelope/room tools.

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