Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

align_object_grid

Snaps an object's world location to the nearest grid increment along chosen axes, enabling precise placement for Blender modeling.

Instructions

Snaps an object's world location to the nearest grid increment along specified axes.

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": "align_object_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo
approvedNo
grid_sizeNoGrid step size in meters.
snap_axesNoAxes along which to apply grid snapping.
request_idNo
object_nameYesName of the target object to snap.
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 implies a mutation of world location but does not say whether the operation is reversible, whether it moves the origin versus geometry, or that the schema's approved/approval_token parameters indicate a gated write workflow that must be satisfied first.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, so there is no waste. However, for a seven-parameter, approval-gated mutation, one sentence is undersized rather than concise, leaving key operational facts unstated.

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?

With no annotations, no output schema, seven parameters at 43% description coverage, and an approval mechanism in the schema, the definition leaves an agent without enough information to call the tool safely or to know what to expect back. Completeness falls well short of the tool's complexity.

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 coverage is only 43%; grid_size, snap_axes, and object_name are documented in the schema, but task_id, approved, request_id, and approval_token are undocumented in both places. The description does not compensate — it never mentions the approval/request-id workflow, which is the most consequential part of invoking this tool correctly.

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 states a specific verb and resource — "Snaps an object's world location" — plus the mechanism (nearest grid increment) and the scoping (specified axes). It is clear on its own, but it never distinguishes itself from plausible siblings such as transform_object or set_object_origin, which an agent could reasonably confuse with it.

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 when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives among the many object-manipulation siblings. The agent must infer that this is the tool for grid-aligned positioning rather than a general transform, purely from the verb "snaps".

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