Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_sculpt_brush

Select the active Blender sculpt brush to apply DRAW, CLAY, GRAB, or other effects during 3D modeling with blend-ai.

Instructions

Set the active sculpt brush.

Args: brush_type: Brush type - DRAW, CLAY, CLAY_STRIPS, INFLATE, GRAB, SMOOTH, FLATTEN, FILL, SCRAPE, PINCH, CREASE, BLOB, MASK, MULTIRES_DISPLACEMENT_SMEAR.

Returns: Confirmation dict with active brush type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brush_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / brush_type / enum
      Added value: +[
+  "BLOB",
+  "CLAY",
+  "CLAY_STRIPS",
+  "CREASE",
+  "DRAW",
+  "FILL",
+  "FLATTEN",
+  "GRAB",
+  "INFLATE",
+  "MASK",
+  "MULTIRES_DISPLACEMENT_SMEAR",
+  "PINCH",
+  "SCRAPE",
+  "SMOOTH"
+]
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only says that the tool sets the active brush and returns a confirmation dict; it does not disclose requirements such as entering sculpt mode, the scope of the change, or any side effects.

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?

The description is front-loaded with the main action and uses clear Args and Returns sections. The enum listing is somewhat redundant with the schema, but the overall structure is efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter setter with an existing output schema, the description covers the action, the parameter values, and the return confirmation. It omits the likely prerequisite of being in sculpt mode, but otherwise contains what an agent needs to invoke the tool.

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 0%, so the description must compensate. It lists all valid brush_type enum values, which documents the parameter's options, but it adds no meaning or explanation beyond the enum values already present in the schema.

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 states a specific verb and resource: 'Set the active sculpt brush.' It is clear what the tool does, but it does not explicitly distinguish itself from the sibling tool set_brush_property, so it misses the highest bar for sibling differentiation.

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?

The description gives no guidance on when to use this tool versus alternatives such as set_brush_property, nor does it state prerequisites like being in sculpt mode. Usage is only implied by the tool name and the concept of an active sculpt brush.

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