Skip to main content
Glama

create_reference_plane

Create offset reference planes parallel to default planes or selected faces to anchor sketches or features at precise distances.

Instructions

Create a reference plane parallel to a default plane or a face.

Two anchoring modes (pass exactly ONE of offset_from / face_centroid_mm):

  1. Default-plane mode — pass offset_from as a default plane name. The new plane is parallel to that source plane, offset by offset_mm.

  2. Face mode (Lote 3 — chained features) — pass face_centroid_mm as a 3-element [x, y, z] from list_faces(). The new plane is parallel to that face, offset along the face's outward normal direction. Use case: anchor a sketch above an angled bracket flange, on a draft surface, or above a previously- extruded boss top.

Args: offset_from: Default plane name — "front" / "top" / "right" (English) or Spanish UI: "Alzado" / "Planta" / "Vista lateral". offset_mm: Signed distance in mm. Positive = along the source plane's normal (or the face's outward normal); negative = opposite. Zero is rejected (would produce a coincident plane). Offsets negativos verificados en vivo (2026-06): ±30 desde "top" producen planos espejo. Para ejes de mate sigue siendo buena práctica el barreno en el origen de la pieza + create_reference_axis("front","right") (cero planos custom). face_centroid_mm: [x, y, z] in mm — face centroid from list_faces().

Returns the new plane's SW-assigned name (e.g., "Plano1"), parent reference, and the signed offset.

Common autoparts use: - Default-plane: rib offsets, fixture-clearance planes, layer references for in-plane mate fixtures. - Face mode: counterbore-on-flange-top, hole pattern offset above an angled bracket flange, layer planes anchored to a previously-extruded surface.

Example — sketch plane 25mm above the Front plane: create_reference_plane("front", 25.0)

Example — sketch plane 10mm above the top of a 50×50×20 block (after list_faces returns the +Z face's centroid): faces = list_faces() top = max( (f for f in faces if f["normal"] and f["normal"][2] > 0.9), key=lambda f: f["centroid_mm"][2], ) create_reference_plane(face_centroid_mm=top["centroid_mm"], offset_mm=10)

Caveat: angled and through-3-points reference planes are still deferred — face + signed offset covers most v1 needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offset_mmNo
offset_fromNo
face_centroid_mmNo
Behavior5/5

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

With no annotations, the description fully bears the behavioral disclosure burden. It explains that the plane is parallel to a source, offset is signed (zero rejected), positive/negative direction meanings, and return value (name, parent, offset). It also mentions testing for negative offsets, providing confidence in behavior.

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 well-structured with headings and bullet points, front-loading the purpose. However, it is somewhat verbose (e.g., Spanish UI names and a cryptic testing note). For a complex tool, it's acceptable, but minor trimming could improve conciseness.

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

Completeness5/5

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

Given 3 parameters, no output schema, and no annotations, the description is exceptionally complete. It covers all modes, parameter details, return value, use cases, and even provides code examples with list_faces integration. An agent has everything needed to use the tool correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must fully explain parameters. It does so thoroughly: offset_from lists allowed plane names (English and Spanish), offset_mm explains sign and zero rejection, face_centroid_mm is described as a 3-element array from list_faces. Examples illustrate usage, meeting the high burden.

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

Purpose5/5

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

The description clearly states the tool creates a reference plane parallel to a default plane or face, distinguishing two modes (default-plane and face mode). It explicitly contrasts with sibling tools like create_reference_axis and mentions deferred methods, making the purpose specific and unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance for each mode: default-plane for rib offsets and fixture-clearance planes; face mode for counterbore-on-flange-top and hole patterns. It also specifies when not to use (angled/through-3-points are deferred) and includes a caveat, leaving no ambiguity for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/MCP_CAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server