dream-creo-mcp

Overview Schema Source Related Servers Discussions Admin

view_set

Turns the active Creo part window to a standard or saved view and refits it for consistent inspection and navigation without capturing an image.

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.

Turn the model's Creo window to a standard view and refit it (no image). Views: front looks along -Z (model XY plane), top looks down -Y, right looks along -X, iso is the Creo default 3D orientation. An unknown view name is an error listing the saved views.

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

Input Schema

Name	Required	Description
`fit`	No
`name`	Yes	Part name without .prt
`view`	Yes	front, back, top, bottom, left, right or iso (Creo default orientation); also a saved view name. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Nov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description does disclose useful behavior: the operation produces no image, it refits the view, and an unknown view name is an error that lists saved views. It does not say whether the view change persists in the model or session, or whether it touches saved state, leaving the side-effect profile partially unstated.

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

Conciseness3/5

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

The tool-specific sentences are tight and information-dense, but roughly two-thirds of the text is a shared preamble about mirroring, units, extrude/revolve, and model_save that is irrelevant to a view operation. The purpose is not front-loaded, forcing the reader past unrelated setup prose to find it.

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 low-complexity, non-destructive view tool with no output schema, the definition covers the outcome (no image), view semantics, and the error case, which is enough to call it correctly. The only real gap is the unexplained 'fit' flag.

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%; the description explains the view directions in geometric terms (front looks along -Z, top down -Y, right along -X, iso is the Creo default) and the part-name convention, which adds meaning. However, the 'fit' boolean parameter is undocumented in both schema and description — 'refit it' implies the behavior but never maps to the parameter or explains how to suppress it.

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?

The second paragraph states a concrete action: turn the model's Creo window to a standard view and refit it, with '(no image)' explicitly separating it from preview_image. It is clear what the tool does, though the actual purpose statement is buried after a long shared preamble about the plugin, units, and mirror behavior that has nothing to do with viewing.

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 '(no image)' parenthetical implies the boundary with preview_image, and the sibling list confirms preview_image exists, but there is no explicit 'use this when you want to orient the view without a screenshot' guidance or statement about when not to use it. Usage is only implied.

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