dream-creo-mcp

Overview Schema Source Related Servers Discussions Admin

model_open

Open an existing Creo part or assembly by folder and name to load the newest version in its own window for viewing or editing.

Instructions

Creates/edits geometry in the running Creo 5 through the DreamFeatureApp plugin. There is no mirror tool: build symmetric shapes with symmetric extrudes, revolves or patterns. Units are mm and degrees. Parts are addressed by name (lowercase, no .prt). Model axes: FRONT is the XY plane (normal +Z), TOP is XZ (normal +Y), RIGHT is YZ (normal +X). Each feature call either ends with an active feature or is rolled back. Nothing is saved unless model_save is called. Check results with model_info (volume, bound_box) and preview_image.

Open an existing dir/name.prt or name.asm (kind=asm), newest version, in its own window.

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": {
      "name": "<name>",
      "dir": "<dir>"
    },
    "name": "model_open"
  }
}

Input Schema

Name	Required	Description
`dir`	Yes	Absolute folder for the .prt file
`kind`	No
`name`	Yes	Part name without .prt

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Nov 6, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden. It usefully states that the newest version is opened, that the model opens in its own window, that unsaved state persists until model_save, and that units are mm/degrees with defined datum axes. It does not say what happens if the file is missing, whether an already-open model is replaced, or how errors surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bulk of the text is global plugin context that applies to all modeling tools (FRONT/TOP/RIGHT axes, symmetric extrusions since there is no mirror, rollback behavior), not to opening a file. The tool-specific instruction is buried in a trailing sentence, so the description is front-loaded with irrelevant material.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter open operation, the key facts (newest version, own window, path construction from dir + name, asm flag, units) are eventually present, but signal is diluted by unrelated modeling guidance and no output schema exists to clarify the return value or failure modes.

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 67%: dir and name are documented in the schema, and the only undocumented enum, kind, is partially explained by 'name.asm (kind=asm)'. The description repeats the schema's no-.prt and lowercase constraint rather than adding new meaning, so it sits at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The actual purpose only appears in the final sentence: 'Open an existing dir/name.prt or name.asm (kind=asm), newest version, in its own window.' The opening sentence, 'Creates/edits geometry in the running Creo 5,' describes a broad modeling workflow and is misleading for a tool that only opens a file, so an agent has to read past contradictory framing to find the real verb+resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus model_new, which is the immediate sibling for creating a model, or versus model_close. The only routing-like statements ('Nothing is saved unless model_save is called', 'Check results with model_info') describe follow-up steps rather than selection criteria.

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