Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_modeling_geometry

Inspect finite Geometry Nodes graph, interface, instance parameters, and base/evaluated geometry fingerprints for a named object and modifier; reports missing modifiers honestly.

Instructions

Read finite Geometry Nodes graph/interface/instance parameters and base/evaluated geometry fingerprints. Missing modifier is reported honestly.

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>",
      "modifier_name": "<modifier_name>"
    },
    "name": "inspect_modeling_geometry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
modifier_nameYes

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, the description carries the full burden. It does establish that this is a non-mutating read ('Read') and that a missing modifier is handled gracefully and reported, which is genuinely useful behavior an agent could not get from structured fields. However, it says nothing about side effects, permissions, or whether inspection triggers evaluation of the node graph, which matters for a tool probing evaluated geometry.

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 short sentences with the core capability front-loaded and the edge-case note second. 'Fingerprints' is jargon and 'reported honestly' is an odd anthropomorphism, but neither adds much bloat. Nothing is wasted.

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, and two fully undocumented parameters, the description leaves key questions open: what a 'fingerprint' actually is in the response, whether both base and evaluated geometry are always returned, and the relationship between the two parameters. For a two-required-param inspection tool with zero structured support, more disclosure is needed.

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% and both parameters (name, modifier_name) are entirely undocumented in the schema. The description mentions a 'modifier' and hints at a graph/interface/instance scope, but never clarifies that 'name' is the object and 'modifier_name' selects the Geometry Nodes modifier, nor what happens if the name itself is wrong. It does not compensate for the coverage gap.

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 uses a specific verb ('Read') and enumerates the resources: Geometry Nodes graph, interface, instance parameters, and base/evaluated geometry fingerprints. That distinguishes it well from the configure_* siblings in the catalog. It stops short of naming an alternative, but the inspect-vs-configure split is inferable from the verb.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named (e.g. inspect_geometry_nodes, inspect_modifier_stack). The only conditional information is that a missing modifier is reported rather than erroring silently. An agent must infer the usage context entirely from the verb 'Read'.

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