Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

scatter_surface_assets

Distributes linked duplicate props across a target surface mesh, aligning them to normals while applying random Z rotation, scale variation, and overlap avoidance for terrain dressing.

Instructions

Distributes linked duplicates of source props across a target surface mesh with surface normal alignment, random Z rotation, scale variation, and overlap avoidance.

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": {
      "surface_name": "<surface_name>",
      "asset_names": "<asset_names>"
    },
    "name": "scatter_surface_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for distribution.
countNoNumber of asset instances to scatter.
task_idNo
approvedNo
max_scaleNoMaximum instance scale multiplier.
min_scaleNoMinimum instance scale multiplier.
request_idNo
asset_namesYesList of source asset object names to distribute.
name_prefixNoNaming prefix for created instances.ScatteredAsset
min_distanceNoMinimum distance between scattered instances to prevent overlap.
surface_nameYesTarget terrain/surface object name to scatter onto.
avoid_overlapNoEnforce minimum distance checking.
approval_tokenNo
align_to_normalNoAlign instance Up vector to surface normal.
collection_nameNoTarget collection for scattered instances.ScatteredAssets
random_rotation_zNoApply random rotation around surface normal / Z axis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 behavioral burden. It does disclose that duplicates are 'linked' (instances share source data) and that instances land in a target collection, which is genuinely useful. But it says nothing about the approval gating implied by the approved/approval_token/task_id/request_id parameters, whether the operation is reversible, whether existing scattered instances are replaced or appended, or any failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the core action and then enumerates modifiers; every clause corresponds to a real capability and there is no filler. Nothing could be trimmed without losing information.

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 mutating tool with no annotations and no output schema, and the description covers only the geometry features. The entire approval/transaction surface (approved, approval_token, task_id, request_id) and the return value (instance names, count created, success state) go unexplained, leaving the agent without enough context to call it correctly or interpret the result.

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 75%, so most parameters are self-documented, and the description usefully maps several of them conceptually (overlap avoidance to min_distance/avoid_overlap, scale variation to min/max_scale, Z rotation to random_rotation_z). It adds no meaning for count, seed, name_prefix, collection_name, or the four approval/transaction parameters, so it does not compensate for the uncovered quarter.

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 ('distributes') and resource ('linked duplicates of source props across a target surface mesh') and enumerates the concrete features applied (normal alignment, random Z rotation, scale variation, overlap avoidance). It is unmistakably a scatter/duplication tool, though it never names a sibling such as align_normals or detail_surface_features to route the agent explicitly.

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 by the feature list: an agent can infer this is for populating a terrain/surface with many prop instances. However, there is no explicit statement of when to choose this over manual duplication, array/grid tools, or a single-object align_normals call, and no stated prerequisites or exclusions.

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