Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

snap_to_ground

Aligns an object's bounding-box bottom precisely to world Z=0 or a specified ground object, with optional vertical offset for exact placement.

Instructions

Aligns an object's bounding box bottom (Z_min) precisely to the ground surface (Z = 0 or the top of a specified ground object) with optional offset.

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

Input Schema

NameRequiredDescriptionDefault
offsetNoVertical offset added above ground surface in meters.
task_idNo
approvedNo
request_idNo
ground_nameNoOptional ground object name. If omitted, snaps to world Z = 0.
object_nameYesName of the target object to align.
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the core transformation precisely (bbox bottom Z_min moved to Z=0 or a ground object's top, plus offset). However, it says nothing about the mutation/approval workflow implied by the approved, approval_token, request_id, and task_id parameters, nor what happens on failure or whether the operation is reversible.

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 with the target anchor and offset qualifier front-loaded and no wasted clauses. It is compact without becoming cryptic.

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 a 7-parameter mutation tool with no annotations and no output schema, the description covers only the geometric behavior. It omits the approval/workflow parameters and any indication of required permissions, which is a material gap for an agent deciding how to invoke it.

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

Parameters2/5

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

Schema description coverage is 43%, so the description should compensate, but it only covers the two already-documented geometric parameters (ground_name, offset). The four workflow-gating parameters — task_id, approved, request_id, approval_token — are undocumented in both schema and description, leaving an agent unable to know whether an approval token must be supplied before the call will succeed.

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 ('Aligns') and a precisely qualified resource ('an object's bounding box bottom (Z_min)') against an explicit target ('Z = 0 or the top of a specified ground object'). It is unambiguous what the tool does, but it never names or contrasts with any sibling such as align_object_grid, so an agent must infer differentiation from the name alone.

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 guidance on when to use this versus alternatives like align_object_grid or align_normals, and no prerequisites or exclusions are stated. Usage is only implied by the verb choice.

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