Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_surface_detail

Inspect surface geometric detail metrics for a Blender mesh object, including roughness, curvature variation, bounding dimensions, topology, and landmark stability; optionally restrict to a region.

Instructions

Inspect surface geometric detail metrics of a designated mesh object, including surface roughness, Laplacian curvature variation, bounding dimensions, topology statistics, and landmark stability.

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": {
      "target_object": "<target_object>"
    },
    "name": "inspect_surface_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_nameNoAlias for target_object.
region_centerNoOptional center coordinate [x, y, z] to restrict inspection to a localized region.
region_radiusNoRadius of region around region_center in meters (0.0 evaluates whole mesh).
target_objectYesName of the target mesh object in the Blender scene.
include_landmarksNoWhether to report stability metrics for stored semantic landmarks.
include_roughnessNoWhether to calculate local surface roughness / Laplacian curvature metric.

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 does not explicitly state that the operation is read-only or non-destructive, nor does it describe permissions, performance characteristics, side effects, or output format.

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 description is a single front-loaded sentence with no filler, and the metric list is useful. It is dense but appropriately sized for the tool.

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?

With six parameters, no annotations, and no output schema, the description identifies the metrics being inspected but does not describe the return structure or how region and include flags affect results beyond the schema. It is adequate but leaves meaningful 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 description coverage is 100%, so the schema already documents all six parameters, including the alias and region controls. The description adds metric vocabulary but does not significantly deepen parameter meaning beyond what the schema provides.

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, 'Inspect', and resource, 'surface geometric detail metrics of a designated mesh object,' then enumerates the metrics included. It does not explicitly distinguish itself from similar siblings such as detail_surface_features or inspect_uv_mesh, so it falls short of a 5.

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 explicit when-to-use guidance, prerequisites, exclusions, or alternatives. Use is only implied by the stated purpose of inspecting surface detail metrics.

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