Skip to main content
Glama

create_reference_axis

Create a reference axis from two plane intersection; use as rotation axis for circular patterns when cylindrical faces are unavailable.

Instructions

Create a reference axis (eje de referencia) at the intersection of two planes — or, where supported, from a single feature reference.

Two ways to call:

  1. Two planes (recommended for v1) — pass both reference_name and reference_2 as plane names. The axis is created at their intersection. Verified live for default-plane combinations (Alzado + Planta, Alzado + Vista lateral, etc.). The most reliable v1 axis source.

  2. Single reference (limited) — pass only reference_name. Currently works for refplane / refaxis feature names, but face/edge names ("Cara@Pieza1") don't resolve in part-document context in this SolidWorks binding. Until face introspection ships, prefer the two-plane path.

World-axis mapping for the two-plane intersection mode. The intersection of two default planes through the origin lies along one of the world axes — which one depends on the pair you pick:

reference_name

reference_2

World axis returned

"front"

"top"

X (left-right)

"front"

"right"

Y (up-down)

"top"

"right"

Z (in-out)

(Spanish UI names map identically: "Alzado"+"Planta" → X, etc.)

For axisymmetric revolves around world X — the standard orientation that build_stepped_shaft and build_revolved_profile assume — use ("front", "top"). This is the same call build_stepped_shaft makes internally (see the construction site at build_stepped_shaft in this file). Picking ("front", "right") instead returns world Y and your revolve will sweep the wrong way around — surface gets rebuilt.

Args: reference_name: Name of the first entity. For two-plane mode, the first plane: "front"/"top"/"right" (English) or "Alzado"/"Planta"/"Vista lateral" (Spanish UI), or a custom "Plano1" from create_reference_plane. reference_2: Name of the second plane for two-plane intersection mode. Same naming rules as reference_name. Pass None for the single-reference mode.

Returns: {"name": "Eje1", "type": "two_plane_intersection" | "from_one_object"}

Use case: define a rotation axis for circular_pattern when you don't have a cylindrical-face name. The intersection of two perpendicular default planes through the origin is a perfectly good axis for any feature centered there.

Example — axis through the part origin (intersection of Front + Top), then 6-instance circular pattern around it: eje = create_reference_axis("front", reference_2="top") circular_pattern(["Cortar-Extruir1"], eje["name"], count=6)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reference_2No
reference_nameYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses behavior: two modes, world-axis mapping, and limitations of single-reference. Lacks error handling details but is otherwise transparent.

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?

Well-structured with headings, table, and example. Somewhat long but every sentence adds value. Slight room for trimming.

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?

Complete for a tool with 2 params, no output schema, and no annotations. Covers all aspects: modes, usage, output format, example, and internal use.

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?

Compensates for 0% schema coverage with detailed parameter explanations, including naming conventions and examples. Clearly explains reference_name and reference_2 semantics.

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 it creates a reference axis from two planes or a single feature. It distinguishes the two modes and provides a use case, differentiating it from sibling tools like create_reference_plane.

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?

Explicitly explains when to use each mode: two-plane recommended for v1, single-reference limited. Provides a use case for circular_pattern and warns about limitations of single-reference mode.

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