Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_modifiers

Reads an object's ordered modifier stack and returns exact typed properties for SUBSURF, BEVEL and SOLIDIFY, flagging other modifier types as unsupported.

Instructions

Read-only ordered modifier stack with exact typed property readback for SUBSURF, BEVEL and SOLIDIFY; other types are identified as unsupported by the typed writer.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key traits: read-only, ordering is preserved, and unsupported modifier types are reported rather than silently ignored. It omits error behavior for a nonexistent or non-object `name` and gives no sense of the response shape or ordering direction.

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?

A single dense sentence with the read-only and ordering constraints front-loaded; no filler. 'Typed writer' is mildly jargon-heavy but still conveys that properties come back in native, exact types.

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 read tool with no annotations and no output schema, the description covers return semantics well enough (ordered stack, exact typed properties, unsupported-type handling) but leaves the sole parameter and failure modes unexplained. Nearly complete, with one consequential hole.

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 the single parameter `name` is documented nowhere — its schema is just a bounded string. The description never explains that `name` identifies the object whose modifier stack is read, so an agent must guess the target of the call from the tool title alone.

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 action and resource: a read-only, ordered modifier stack with typed property readback, restricted to SUBSURF, BEVEL and SOLIDIFY. This is far more specific than a generic 'inspect' label. The gap is that it never distinguishes itself from the sibling `inspect_modifier_stack`, whose name implies nearly identical behavior.

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 is named. The only inferable guidance is negative scoping (read-only, three supported types), which tells an agent when this tool will not work but not when to prefer it over `inspect_modifier_stack` or `apply_modifier`.

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