Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

new_part

Creates a new empty millimetre part at the specified absolute .prt path and makes it the active work part for NX modeling.

Instructions

Create a new, empty millimetre part and make it the work part.

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": "new_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path of the .prt file to create, e.g. C:\\work\\bracket.prt. Must not exist yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the side effect that the new part becomes the active work part, but says nothing about what happens to an already-open part, failure conditions, permissions, or what the call returns.

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

Conciseness5/5

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

One front-loaded sentence with the creation action, the resulting object type, and the work-part side effect. No wasted wording.

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 simple one-parameter creation tool, the core behavior is covered. However, with no annotations and no output schema, the description should clarify the outcome of the call and what happens to any currently active part, which it does not.

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 100% and the sole path parameter is thoroughly documented in the schema, including the absolute-path format and the 'must not exist yet' constraint. The description adds no meaning beyond that, so the baseline 3 applies.

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?

Specific verb and resource: 'Create a new, empty millimetre part', plus the scope detail that it becomes the work part. This implicitly separates it from open_part, though it does not name the sibling or state the distinction explicitly.

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 phrase 'new, empty' implies this is for starting a part from scratch rather than opening an existing one, but there is no explicit when-to-use vs when-not-to-use guidance and no named alternative such as open_part.

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