Skip to main content
Glama
vino3dx
by vino3dx

mod_ffd_3x3x3

Destructive

Apply a 3x3x3 free-form deformation lattice with 27 control points for finer object shaping than 2x2x2. Works on selected objects or specified names.

Instructions

自由变形修改器 3x3x3:27 个控制点,比 2x2x2 更细腻。 [English] Free-form deform 3x3x3: 27 control points, finer than 2x2x2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo修改器名。 | Modifier name.
objectsNo对象名列表;省略则使用当前选择。 | Object names; omit for selection.
autoExtentNo自动适配对象范围,默认是。 | Auto-fit to object extent, default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds the 27-control-point detail but does not explain side effects such as stack changes, object requirements, or reversibility.

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

Conciseness5/5

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

The description is compact, bilingual, and front-loads the essential 3x3x3/27-point information. Every clause contributes detail rather than filler.

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 three-parameter tool with fully described optional parameters and a known destructive annotation, the description is mostly sufficient. A short mention that this applies the modifier to the given/selected objects would make it complete.

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 coverage is 100% with descriptions for name, objects, and autoExtent, so the schema carries the parameter-documentation burden. The description adds no parameter-level meaning beyond the modifier's resolution.

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 identifies the tool as a 3x3x3 free-form deformation modifier with 27 control points and explicitly differentiates it from the coarser 2x2x2 variant. It lacks an explicit action verb such as 'adds/applies', but the modifier nature and resolution are clear.

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

Usage Guidelines3/5

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

The phrase 'finer than 2x2x2' gives an implied recommendation for finer deformation, but there is no explicit statement of when to choose this tool over mod_ffd_4x4x4 or other modifiers. Neither conditions nor exclusions are provided.

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