Skip to main content
Glama

sculpt.displace

blender_sculpt_displace

Displace selected mesh geometry by a specified strength and direction in Blender, enabling precise sculpting adjustments through secure, recoverable operations.

Instructions

PartMe Blender Harness command sculpt.displace. Risk: standard; maturity: L3. Requirements: Per-request argument checks and session policy still apply

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strengthYes
directionNoThree finite numbers; rotation uses radians
selectionYesSelection receipt returned by mesh.select
_requestIdNoStable request id for replay safety
_authorizationNoAction-bound Harness authorization claim
_transactionIdYesHarness milestone transaction id
_expectedSceneRevisionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior2/5

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

Annotations provide readOnlyHint=false, destructiveHint=false, etc. Description adds only 'Risk: standard; maturity: L3' which is not behavioral. It does not contradict annotations but adds minimal context. The statement about per-request argument checks is vague and generic, not specific to this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is not effective conciseness; it is under-specification. It lacks structure and fails to front-load essential information about the tool's function. It does not earn its place.

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

Completeness1/5

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

For a tool with 7 parameters, a nested selection object, and an output schema, the description is completely inadequate. An agent cannot determine what the tool does, what input is expected, or what it returns. The description fails to provide any contextual completeness.

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 has 71% coverage, and description adds no parameter semantics. It doesn't clarify any parameters beyond what the schema already provides. Since coverage is moderate (not high), the description should compensate but doesn't, leaving some parameters without added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely restates the command name 'sculpt.displace' without explaining what the tool does. It gives no verb, resource, or effect. It is essentially a tautology, providing no functional clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus other sculpt tools like blender_sculpt_brush_stroke. No context, prerequisites, or alternatives mentioned. The agent is left without any decision support.

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