Skip to main content
Glama
vino3dx

3dsmax-mcp

by vino3dx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_chamferbox

Destructive

Create a chamfered box in 3ds Max with adjustable bevel amount. Requires Extended Primitives enabled; bevel faces raise polygon count, so keep chamfer low for game assets.

Instructions

创建一个带圆角的长方体（拓展基础体）。chamfer 控制倒角，圆角面会显著增加多边形数。若当前 Max 未启用拓展基础体则会报错提示。 [English] Create a chamfered box (extended primitive). chamfer controls the bevel; bevel faces add many polygons. Errors gracefully if Extended Primitives are not enabled in this Max.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo结束角（度，Arc）。 | End angle in degrees (Arc).
axisNo壶轴类型 1-4（Teapot）；忽略通常即可。 | Teapot axis 1-4; usually leave default.
fromNo起始角（度，Arc）。 | Start angle in degrees (Arc).
nameNo对象名称；省略则自动命名。 | Object name; auto-generated if omitted.
sidesNo边数/管径向分段（Cylinder/Cone/NGon/Torus）。 | Side / tube radial segments (Cylinder/Cone/NGon/Torus).
turnsNo圈数（Helix）。 | Number of turns (Helix).
widthNo宽度。 | Width.
filletNo圆角量（Capsule）。 | Fillet amount (Capsule).
heightNo高度。 | Height.
lengthNo长度（Box/Plane/Rectangle/Cone 等）。分段数决定多边形数量，游戏资产保持 12-16。 | Length (Box/Plane/Rectangle/Cone etc). Segments drive poly count - keep 12-16 for game assets.
radiusNo半径（Sphere/Torus/Cylinder 等）。 | Radius (Sphere/Torus/Cylinder etc).
smoothNo是否平滑（Teapot 等）。 | Smooth the surface (Teapot etc).
capSegsNo封顶分段（Cylinder/Cone/Tube）。 | Cap segments (Cylinder/Cone/Tube).
chamferNo倒角量（ChamferBox）。 | Chamfer amount (ChamferBox).
radius1No第一半径（Donut/Tube/Helix/Cone 顶）。 | First radius (Donut/Tube/Helix/Cone top).
radius2No第二半径（Donut/Tube/Helix/Cone 底）。 | Second radius (Donut/Tube/Helix/Cone bottom).
setNameNo创建后再改名为此名（name 的兜底写法）。 | Rename after creation (fallback for name).
positionNo世界坐标位置 [x,y,z]。 | World position [x,y,z].
segmentsNo分段数；影响多边形数量，游戏资产保持低值。 | Segment count; drives polygon count, keep low for game assets.
widthSegsNo宽度方向分段（Box/Plane）。 | Width segments (Box/Plane).
heightSegsNo高度方向分段（Box/Cylinder/Cone）。 | Height segments (Box/Cylinder/Cone).
lengthSegsNo长度方向分段（Box/Plane）。 | Length segments (Box/Plane).
cornerRadiusNo圆角半径（Rectangle）。 | Corner radius (Rectangle).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that bevel faces 'add many polygons' and that the tool errors if Extended Primitives are not enabled. This provides useful previewable consequences. It does not contradict the readOnlyHint=false or destructiveHint=true annotations.

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 and front-loaded: it names the object type, explains the key parameter's effect, warns about polygon cost, and states the error condition. The bilingual duplication is purposeful and each clause earns its place.

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 23-parameter tool with no output schema, the description covers the core behavior, the key parameter, a performance concern, and a prerequisite condition. It is not exhaustive about ignored parameters or defaults, but the high schema coverage mitigates that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that chamfer controls the bevel, not just the amount, and warns that bevel faces increase polygon count. This is valuable contextual semantics for the most relevant parameter.

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: 'Create a chamfered box (extended primitive)'. It clearly distinguishes this from a standard box by mentioning 'extended primitive' and 'chamfer', though it does not explicitly name create_box as the alternative for non-chamfered boxes.

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?

Usage is implied by the purpose: use this when creating a chamfered box. The description adds a prerequisite condition ('Errors gracefully if Extended Primitives are not enabled'), but does not explicitly compare against sibling tools like create_box or state when not to use this tool.

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