Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Export model to file

export_model
Read-only

Exports a Part Studio or Assembly to STEP, STL, Parasolid, or IGES on the server and returns the file path without modifying the document.

Instructions

Export a Part Studio or Assembly to a CAD/mesh file (STEP, STL, Parasolid, IGES) on the machine running this server and return the file path. Does not modify the document. STL sizes follow the configured unit system.

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": {
      "document_id": "<document_id>",
      "element_id": "<element_id>"
    },
    "name": "export_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput file format.STEP
filenameNoFile name without directory (default: the element ID). Saved under the server's output directory.
part_idsNoExport only these parts (Part Studios only). Default: everything.
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
document_idYesOnshape document ID: the 24-character hex string after /documents/ in the document URL. Get it from list_documents.
workspace_idNoWorkspace ID (the string after /w/ in the URL). Optional - defaults to the document's main workspace.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already covered; the description adds real context on top: the file is written to the machine running the server, the file path is returned, and STL dimensions follow the configured unit system. It stops short of describing overwrite behavior when a filename already exists or whether the export is synchronous.

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?

Three short sentences with the core action and formats front-loaded, followed by the non-mutation guarantee and the one non-obvious sizing caveat. Nothing is redundant or padding.

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?

An output schema exists and the description still confirms a file path is returned, so return-value handling is covered. For a six-parameter export tool with a 100%-covered schema, the remaining minor gap is overwrite/naming collision behavior and permissions, which keeps it short of a 5.

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 all six parameters including format enum, filename, part_ids, and workspace defaulting are already documented in the schema. The description adds only the STL unit-system note, which is marginal rather than compensating detail, so the baseline of 3 applies.

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 names a specific verb and resource ("Export a Part Studio or Assembly") plus concrete output formats (STEP, STL, Parasolid, IGES) and the destination (a file on the server, path returned). An agent knows exactly what this produces and where it lands, and no sibling tool offers anything comparable.

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?

Usage is implied by the verb and by the note that the document is not modified, which tells the agent this is a safe non-mutating read. There is no explicit when-to-use versus when-to-not guidance, no prerequisites (workspace selection, permissions), and no mention of alternatives in the sibling set.

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