Skip to main content
Glama

Export Shape

export_shape
Destructive

Exports a FreeCAD shape to STEP, IGES, BREP, or STL, inferring the format from the file extension. Omit the object to use the document's single final shape; multiple final shapes raise an error.

Instructions

Export a shape to STEP/IGES/BREP/STL. Format inferred from path extension.

object: FreeCAD object name (NOT a AnkusDrive handle). If omitted, exports the document's single final shape: inputs consumed by another feature (a cut's base/tool, Body features) are skipped, and solids win over sketches. If more than one final shape remains, it raises and lists them. It never picks one for you.

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": {
      "path": "<path>"
    },
    "name": "export_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
objectNo
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.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the write-to-disk nature is covered structurally; the description adds real behavior beyond that: format is inferred from the path extension, ambiguous final shapes raise an error listing the candidates, and it explicitly refuses to guess. It does not say what happens if the target file already exists (overwrite?) or whether parent directories are created, which matters for a file-writing tool.

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?

Purpose and format rule are front-loaded in one tight sentence, followed by the object-resolution rules. The second paragraph is dense but each clause (skipped inputs, solids over sketches, raise-and-list on ambiguity) carries distinct information; only the parenthetical about handles is slightly awkwardly worded.

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 three-parameter tool with no output schema, the description covers the hard part (object resolution and error behavior) thoroughly and implies the return is the written file. Gaps remain around overwrite behavior, the workspace parameter, and confirmation of what the call returns, but nothing essential to invoking it correctly is missing.

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 only 33%, with only 'workspace' documented in the schema, so the description has to compensate. It does so strongly for 'object' (FreeCAD object name, not a handle, plus the exact skip/priority rules for omission) and implies 'path' drives format selection, but it never explains the 'workspace' parameter that appears in the schema, leaving one of three parameters unaddressed.

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?

States a specific verb (export) plus the resource (a shape) and enumerates the concrete output formats STEP/IGES/BREP/STL, which distinguishes it from sibling exporters like export_drawing, sheet_flat_export, and journal_export. An agent can identify the correct tool without opening the schema.

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 gives detailed guidance on which object is exported when the parameter is omitted, which is effectively selection guidance within the tool. However, it never states when to prefer this over the other export tools (export_drawing, sheet_flat_export) or any precondition such as an open document or existing file path.

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