Skip to main content
Glama

Make Datum Plane

make_datum_plane

Create a datum plane in a FreeCAD body using XY, XZ, or YZ origin planes or a tagged face, with an optional offset along the plane normal for precise sketch and feature placement.

Instructions

Create a Datum Plane in a Body.

base: 'XY' | 'XZ' | 'YZ' for body origin planes. Pass a face_tag dict {handle, tag} for attachment to a face on another shape. offset: shift along the plane normal in mm.

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": {
      "body": "<body>"
    },
    "name": "make_datum_plane"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoXY
bodyYes
nameNoDatumPlane
offsetNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive, non-open-world creation call, so the safety profile is covered. The description adds useful mode-specific context (origin-plane vs. face attachment, offset direction in mm) but says nothing about whether creation requires an active document, what happens if the body is missing, or that a handle is produced for later reference.

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 action is front-loaded in one sentence, followed by compact per-parameter notes with no filler. The telegraphic fragment style is efficient, though the base/face_tag conflation slightly muddies an otherwise tight layout.

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?

For a five-parameter creation tool with no output schema, the description covers what it makes, both attachment modes, and unit-bearing displacement. The remaining unknowns (return value, active-document requirement) are minor and partly absorbed by annotations declaring a non-destructive write.

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 only 20% (only 'workspace' is documented), so the description must compensate and it partly does: it explains 'base' values, the face_tag dict form, and that 'offset' is in mm along the plane normal. Still, 'body' (the sole required parameter) and 'name' are never addressed, and the claim that 'base' takes a {handle, tag} dict conflicts with the schema's string type, which could mislead an agent.

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 first sentence gives a specific verb+resource ('Create a Datum Plane in a Body'), which is unambiguous and distinguishes it from siblings like make_sketch or make_body. It doesn't explicitly state the relationship to those siblings (e.g. that a datum plane is typically a sketch support), but the resource is concrete enough for an agent to select it correctly.

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 description explains the two modes of use (origin planes via 'XY'/'XZ'/'YZ' vs. face attachment via a face_tag dict) and the offset meaning, so usage is implied reasonably well. However, it never says when to prefer this over alternatives such as building a sketch on an existing face, nor does it state prerequisites like needing an active document/body.

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