Skip to main content
Glama
RoxyCoding

Roxy Blender MCP

by RoxyCoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_lathe

Create round 3D forms by revolving a 2D profile around the Z axis—ideal for bottles, vases, bowls, knobs, and columns.

Instructions

Surface of revolution around the local Z axis - the best tool for anything round: bottles, vases, cups, bowls, lamp bases, knobs, wheels, columns, chess pieces, light bulbs. Example vase: profile=[[0,0],[0.06,0],[0.09,0.06],[0.1,0.13],[0.05,0.24],[0.04,0.28],[0.05,0.3]], cap=false, thickness=0.004.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoClose open ends that are off the axis with flat caps.
nameNoLathe
angleNoSweep angle in degrees (<360 for partial revolves).
bevelNoRounded edges via an angle-limited Bevel modifier with hardened normals: width in metres (e.g. 0.002 for a 10 cm part), or {width, segments, angle}. true = automatic width.
closedNoProfile is a closed loop (e.g. a thick ring/torus-like section).
originNoWhere the origin sits on the part's bounding box: center, bottom, top, left, right, front, back, min, max, or keep (geometry coordinates exactly as given). origin='bottom' + location z=0 stands a part on the floor.keep
parentNo
profileYesHalf-silhouette as [[radius, z], ...] from bottom to top (metres). radius 0 closes the end on the axis. Add a third value 1 to make a point a hard corner, e.g. [0.04, 0, 1]; turns sharper than 60 deg are corners automatically (flat bottoms stay flat). A handful of points is enough: they are smoothed with a centripetal spline.
shadingNoauto = smooth with sharp edges kept above smooth_angle (best default); smooth; flat.auto
locationNoWorld position [x,y,z] (metres) of the object origin.
materialNoMaterial preset name (list_material_presets), or {preset, color, roughness, weathering, ...} like apply_material, or the name of an existing material. Presets with a real-world scan use Poly Haven automatically; {'polyhaven': 'mossy rock'} picks any Poly Haven texture by description.
rotationNoRotation [x,y,z] in degrees.
segmentsNoSteps around the axis (64 = smooth).
thicknessNoWall thickness (Solidify, inward) - use for vessels with an open top (cap=false).
collectionNo
resolutionNoSpline samples between control points.
subdivisionNoSubdivision Surface levels (1-3) for soft/organic shapes.
smooth_angleNo
interpolationNosmooth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden but only describes the geometry produced. It never states that a new object is added to the scene, whether an existing object is replaced, permission/collection effects, or failure modes. The worked example helps but does not substitute for behavioral disclosure.

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 core definition is front-loaded in the first clause, followed by use cases and a compact worked example. It is appropriately sized for a creation tool with no wasted preamble.

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?

For a complex 19-parameter creation tool with no annotations and no output schema, the description conveys the core concept and a usable example but omits behavioral context (object creation semantics, interaction with location/origin). It is adequate but has clear gaps an agent would need to infer.

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 74%, so most parameters are already documented, and the description's example (profile, cap=false, thickness) mostly illustrates values the schema already explains. It adds marginal tie-together value by showing a coherent vessel configuration but introduces no new semantics for the 19 parameters.

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 geometric verb+resource ('surface of revolution around the local Z axis') and enumerates concrete products (bottles, vases, columns), so an agent understands exactly what it builds. It does not explicitly distinguish itself from creation siblings like create_sweep, create_loft, or create_pipe, so it falls short of the 'differentiates from siblings' bar.

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

Usage Guidelines4/5

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

The phrase 'the best tool for anything round' plus a long list of example objects gives clear context for when to reach for this tool. It does not name a when-not condition or an alternative sibling for near-miss shapes (e.g. tubes/revolved pipes), so it misses the top tier.

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