Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

create_offset_plane

Create a reference plane parallel to a selected plane or flat face at a specified offset distance, then use the returned plane name to start a sketch.

Instructions

Create a reference plane parallel to a plane or to a flat face of the body, at a given distance. Returns the new plane's name, to use with create_sketch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "distance": "<distance>"
    },
    "name": "create_offset_plane"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoOffset in the opposite direction
unitNomm, cm, m, inch or ft
face_xNoX of a point on the face (reference='face' only)
face_yNoY of a point on the face (reference='face' only)
face_zNoZ of a point on the face (reference='face' only)
distanceYesOffset distance (negative flips the direction)
referenceNoFront, Top, Right, a plane name (e.g. 'Plane1'), or 'face' to offset from the flat face at face_x/face_y/face_zFront

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses that this is a creation operation and that it returns the new plane's name, but says nothing about side effects, whether duplicate planes are created on repeat calls, what happens on an invalid reference, or permission/link requirements.

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?

Two short sentences, both front-loaded: the core action first, then the return value and its downstream use. No redundant restatement of the tool name or filler text.

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 7-parameter creation tool with no annotations and no output schema, the definition covers purpose, the offset semantics and the return value, and the schema fills in the rest of the parameters. It falls short only on failure modes and on which document (part vs assembly) the plane lands in.

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 description coverage is 100%, so every parameter (flip, unit, face_x/y/z, distance, reference) is already documented in structured data. The description adds only the notion of an offset distance and that the plane may be anchored to a flat face, which is already conveyed by the reference parameter description. Baseline 3 applies.

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?

States a specific verb and resource: it creates a reference plane that is parallel to a plane or flat face at a given offset distance. It also names the return value (the new plane's name), which lets an agent distinguish it from geometry-creating siblings, though it never explicitly contrasts itself with alternatives such as create_sketch_on_face.

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 clause 'to use with create_sketch' hints at the workflow position (obtain a plane name before sketching), so usage is implied rather than stated. There is no guidance on when to choose this over offsetting from a face coordinate triple versus a named plane, and no prerequisites or exclusions are given.

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