Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_sculpt_state

Reads the object's sculpt mode, active brush settings, dynamic-topology flag, voxel size, and a stable base mesh snapshot so you can verify sculpt state before editing.

Instructions

Read sculpt mode, active brush settings, dynamic-topology flag, voxel size and stable base mesh snapshot.

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

Input Schema

NameRequiredDescriptionDefault
object_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 must carry the whole behavioral burden; it does establish that this is a non-mutating read by leading with 'Read'. It falls short on what the 'stable base mesh snapshot' actually is (a copy? a reference? how large?), and says nothing about errors if the object isn't in sculpt mode.

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 front-loaded sentence listing the returned state fields with no filler; the field list is the right thing to put first. The phrase 'stable base mesh snapshot' is the one vague spot that keeps it from a 5.

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?

No output schema exists, so the description acts as the return-value contract, and it does enumerate five categories of state returned. It still leaves the snapshot concept and the behavior when the object lacks sculpt data unexplained, which matters for a tool whose whole job is reporting state.

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%, so the description should compensate for the single undocumented parameter, yet it never mentions object_name, its length constraint, or which object types are valid. The name 'object_name' is largely self-explanatory, which keeps this from scoring 1, but the description adds no meaning beyond the field name.

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 exactly what state is retrieved: sculpt mode, active brush settings, dynamic-topology flag, voxel size, and a base mesh snapshot. That distinguishes it from the mutating siblings like sculpt_mesh, but it never contrasts itself with the other inspect_* siblings (inspect_modeling_geometry, inspect_surface_detail), so an agent must infer boundaries from names alone.

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 guidance, no precondition such as 'object must be a mesh' or 'object must be in sculpt mode', and no named alternative. The 'Read' verb implies a non-mutating inspection call, but nothing tells the agent when to pick this over inspect_modeling_object or sculpt_mesh.

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