Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_curve_geometry

Reads actual curve, text spline, control-point and setting data plus independently evaluated mesh fingerprints/counts, including converted mesh copies, for geometry verification in Object Mode.

Instructions

Read actual finite curve/text spline/control-point/settings and independently evaluated mesh fingerprint/counts; also inspects converted mesh copies. Object Mode only.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Read' implies a non-mutating operation and 'Object Mode only' discloses a mode prerequisite. It also reveals a meaningful trait – that mesh counts are 'independently evaluated' rather than merely read, and that converted mesh copies are handled. Missing are error/absence behavior (e.g., non-curve object or unknown name) and what a 'fingerprint' actually is.

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?

Everything is packed into one dense semicolon-joined sentence with an odd leading qualifier ('actual finite'). The core information is front-loaded, but the phrasing costs clarity for the space it saves.

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?

For a one-parameter inspection tool with no output schema, the description does a fair job of enumerating what comes back (control points, settings, mesh counts), partially substituting for a return schema. Gaps remain around the meaning of the name argument and failure modes, and no annotations exist to cover the safety profile.

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 0% for the single required parameter, so the description must compensate and does not. It never clarifies whether 'name' is the object name, the curve data-block name, or a path, nor what happens if the name does not match a curve; the maxLength 63 constraint is left unexplained.

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 ('Read'/'inspects') and enumerates the resources returned: curve/text spline data, control points, settings, and mesh fingerprint/counts. It is distinguishable from the configure_curve_geometry sibling by the inspection framing, though it never names an alternative. Phrasing like 'actual finite curve' is somewhat garbled and blurs an otherwise clear purpose.

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 one explicit guideline is the precondition 'Object Mode only', which is genuinely useful context for invocation. However, there is no statement of when to choose this over inspect_geometry_nodes, inspect_modeling_geometry, or configure_curve_geometry, so the usage decision is only implied.

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