Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

export_document

Exports the active Inventor document to a neutral CAD file (STEP, IGES, SAT, or STL) for customers, vendors, or printers. The original document remains unchanged.

Instructions

Write the active document to a neutral CAD file, for a customer, a vendor or a printer. An existing file at path is replaced; the file is checked afterwards and its size returned. The Inventor document itself is unchanged — save_document saves that. For the laser use export_flat_pattern, for a parts list export_bom, for a PDF create_drawing.

Args: path: Output file, e.g. "D:/export/part.step". format: STEP, IGES, SAT or STL.

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_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
formatNoSTEP
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it discloses the critical trait that an existing file at path is overwritten, plus post-write verification and the returned size. It also clarifies the source document is not modified. It stops short of permission or failure-mode behavior, keeping it from a 5.

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 behavior and routing information is front-loaded in the first paragraph, with parameter detail deferred to an Args block. Slight redundancy with the schema's path field, but no sentence is padding.

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?

An output schema exists, so the brief note about the returned file size is sufficient. Between the description and schema, an agent knows the overwrite consequence, the format choices, instance selection, and that the source document is untouched.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, but the description compensates: it gives a concrete path example and enumerates the valid format values (STEP, IGES, SAT, STL), which the schema does not list. The instance parameter is already documented in the schema, so nothing important is left uncovered.

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?

Specific verb and resource ('write the active document to a neutral CAD file') with an explicit contrast against save_document, which handles the native document. An agent can distinguish this from export_flat_pattern, export_bom and create_drawing without inspecting any schema.

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?

Names the use case (customer, vendor, printer) and routes each alternative case explicitly: laser to export_flat_pattern, parts list to export_bom, PDF to create_drawing, persistence to save_document. The selection conditions are stated rather than inferred.

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