Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_terrain

Generates parameterized landscape terrain meshes with multi-octave procedural elevation, surface shading, boundary falloff, and evaluated elevation metrics for Blender scenes.

Instructions

Generates a parameterized landscape terrain mesh with multi-octave procedural elevation, smooth shading, boundary falloff damping, and evaluated elevation metrics.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the terrain object.LandscapeTerrain
seedNoDeterministic random seed for procedural noise.
depthNoTerrain depth along Y axis in meters.
widthNoTerrain width along X axis in meters.
task_idNo
approvedNo
locationNo
roughnessNoFractal roughness multiplier per octave.
request_idNo
noise_scaleNoBase frequency of procedural noise.
resolution_xNoVertex resolution along X axis.
resolution_yNoVertex resolution along Y axis.
noise_octavesNoNumber of fractal noise octaves.
approval_tokenNo
elevation_scaleNoMaximum elevation displacement height in meters.
boundary_falloffNoSmoothly dampen elevation to zero at boundaries.

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 behavioral burden. It mentions procedural elevation, smooth shading, boundary falloff, and evaluated metrics, but it does not disclose side effects, scene mutation behavior, permissions, computational cost, or what is returned.

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 definition is a single dense sentence with no filler and the core operation is front-loaded. A few terms such as 'evaluated elevation metrics' are somewhat opaque, but the description avoids unnecessary 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?

This is a 16-parameter creation tool with no annotations and no output schema, so the description needs to do more than state the generated features. It omits important context about scene effects, approval-related parameters, return values, and when the operation should be used.

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 description coverage is 69% across 16 parameters, so many parameters are already documented in the schema. The description adds useful meaning for noise, elevation, and falloff behavior, but it does not explain the roles of name, dimensions, resolution, location, task/approval fields, or request identifiers beyond what the schema states.

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 gives a specific verb and resource: generates a landscape terrain mesh with procedural elevation and related terrain features. This clearly distinguishes it from generic mesh creation such as create_primitive, though it does not explicitly name sibling alternatives.

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 offers no when-to-use guidance, no exclusions, and no alternatives. It does not tell an agent when terrain generation should be chosen over create_primitive or other scene-creation 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