Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_semantic_landmarks

Inspects semantic landmarks on a mesh, reprojects them onto calibrated FRONT, SIDE, and TOP views, and measures per-view and aggregate reprojection error to verify landmark alignment.

Instructions

Inspect configured semantic landmarks on a mesh object. Computes current 3D positions, reprojects them onto calibrated 2D reference views (FRONT, SIDE, TOP), and measures per-view and aggregate reprojection error (RMSE and mean error).

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

Input Schema

NameRequiredDescriptionDefault
viewsNoOptional list of views to evaluate reprojection error for. Defaults to all configured views.
task_idNoOptional task or workflow identifier.
object_nameNoAlias for target_object.
target_objectYesName of the target mesh object in the Blender scene to inspect.
include_projection_detailsNoWhether to return detailed per-landmark per-view reprojection coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose substantive behavior beyond the name: computing current positions, reprojecting onto calibrated views, and returning per-view and aggregate error metrics. But it never states that the operation is read-only (no scene mutation), nor any cost, prerequisites for 'calibrated' views, or failure behavior when landmarks are unconfigured.

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?

Two sentences, front-loaded with the object being inspected before the computational detail. Every clause carries information about what is computed and measured; no filler, though it could be slightly tighter.

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 no output schema and no annotations, an agent must infer read-only safety and return shape. The description does describe the metrics returned (RMSE, mean error, per-view and aggregate) and include_projection_details hints at detail level, but the absence of any stated side effects or output structure for a 5-parameter tool leaves real 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 every parameter including the views enum, aliases, and include_projection_details. The description adds only indirect meaning (that views relate to reprojection error, that error is RMSE/mean), so baseline 3 is appropriate.

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 and resource: 'Inspect configured semantic landmarks on a mesh object,' then details exactly what is computed (3D positions, reprojection onto FRONT/SIDE/TOP views, RMSE/mean error). It implicitly differentiates from siblings like configure_ and detect_semantic_landmarks by framing this as inspection, though it never names an alternative 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?

The 'inspect' framing and the mention of 'configured' landmarks imply this is a read/verification step after landmarks are configured, and the reprojection-error focus implies use for calibration QA. However, there is no explicit when-to-use, when-not-to-use, or named alternative to redirect an agent.

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