Skip to main content
Glama
520-YM

codex-creo-mcp

by 520-YM

creo_switch_current_project_component_visibility

Destructive

Switch visibility of two subassembly components in an active Creo session: suppress one and resume another, verifying the expected assembly state before saving.

Instructions

在当前五个零总装配范围内,通过常驻 Creo API 将指定子装配中的一个活动组件隐含,同时将另一个普通隐含组件恢复。工具按组件模型名唯一定位并核对原状态,原子执行、读回验证、重新生成和保存子装配及总装配、返回总装配,并把这两个装配模型族的旧版本移入回收站。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resume_componentYes
expected_assemblyYes
suppress_componentYes
Behavior5/5

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

注释已表明 destructiveHint=true,描述进一步披露了原子执行、读回验证、重新生成并保存子装配与总装配、返回总装配,以及将旧版本移入回收站等关键副作用。这些信息显著超出注释本身,帮助代理预判破坏性后果。

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?

描述是一个长而密集的句子,但每个分句都承载有效信息,如原子执行、保存、回收站行为。没有冗余,不过可以拆分为更清晰的结构。

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?

在无输出 schema 且参数无描述的情况下,描述已覆盖操作范围、副作用、验证方式、保存行为和返回值。但仍缺少对 expected_assembly 的明确界定及失败/异常行为,稍有遗漏。

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 覆盖率为 0%,描述承担了参数解释责任。它说明了组件按模型名唯一定位,并区分了“活动组件”和“普通隐含组件”,对应 suppress_component 与 resume_component。但 expected_assembly 的具体含义(总装配还是子装配模型名)仍然模糊,未逐一阐明参数。

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?

描述明确说明了具体操作:在指定子装配中隐含一个活动组件并恢复另一个隐含组件,且界定了当前总装配范围。与兄弟工具中围绕特征复制/抑制的 create_safe_feature_suppression_copy 等相比,本工具针对组件可见性切换,易区分。

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?

描述给出了清晰的使用场景:当前项目总装配内、指定子装配中,需要同时抑制和恢复组件时使用。但没有明确说明何时不应使用或列出替代工具,因此未达到最高分。

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/520-YM/codex-creo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server