dream-creo-mcp

Overview Schema Source Related Servers Discussions Admin

model_close

Erase a model from the Creo session by name. Refuses models with unsaved changes unless confirm=DISCARD_CHANGES is passed.

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.

Erase the model from the Creo session. A model with unsaved changes is refused (unsaved_changes) unless confirm=DISCARD_CHANGES. Only close models you created in this conversation or the user named.

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>"
    },
    "name": "model_close"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Part name without .prt
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Nov 6, 2026

TDQS

A3.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 load and does well: it names the failure mode (refused with unsaved_changes), the exact override (confirm=DISCARD_CHANGES), and limits the blast radius to the live session. It stops short of stating explicitly that the .prt file on disk is untouched and whether the tool is reversible.

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?

Roughly two-thirds of the text is generic session boilerplate about mirror alternatives, mm/degrees units, FRONT/TOP/RIGHT planes, and feature rollback, none of which applies to closing a model. The actual purpose appears only in the second paragraph, so the definition is neither front-loaded nor waste-free.

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 two-parameter destructive tool with no output schema, the description covers purpose, guardrail, refusal condition, override spelling, and result verification via model_info and preview_image. Only the on-disk persistence question and full confirm value set remain unstated.

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 50%: name is documented in the schema, but confirm has only type "string" with no allowed values. The description supplies the one known value, DISCARD_CHANGES, which is genuine added meaning, but leaves open whether any other value is accepted and what a wrong value does.

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?

"Erase the model from the Creo session" gives a specific verb (erase), resource (model), and scope (session, not disk), which distinguishes it from delete_feature without naming that sibling. The opening boilerplate paragraph about geometry creation, axes, and units does not describe closing and dilutes the signal, but the operative sentence is unambiguous.

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

Usage Guidelines4/5

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

"Only close models you created in this conversation or the user named" is an explicit eligibility boundary for when this tool may be used. Combined with "Nothing is saved unless model_save is called," an agent can infer it should save first, though model_save is never named as the alternative step.

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