Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

sketch_line

Adds a straight line between two [x, y] points in a named sketch using millimeter coordinates to define sketch geometry for NX models.

Instructions

Add a straight line to a sketch.

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": {
      "sketch": "<sketch>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "sketch_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd point [x, y] in sketch coordinates (mm)
startYesStart point [x, y] in sketch coordinates (mm)
sketchYesSketch name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'Add' implies a mutation of persistent model state, but the description never states whether the sketch must exist or be open, whether the operation is idempotent or reversible, what units/precision are enforced, or what is returned. For an unannotated mutation tool this is a substantial gap.

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?

One short, front-loaded sentence with no waste — the verb and object lead. It is efficient but so terse that the brevity comes at the cost of guidance rather than serving it.

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?

The tool is simple (three required, fully documented parameters, no nested objects) and has no output schema to explain, so the schema covers most of what an agent needs. However, with no annotations and no statement of side effects or return value, the definition is only minimally sufficient for a state-mutating CAD operation.

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 description coverage is 100%, with start/end explicitly documented as [x, y] in millimetres and sketch as a sketch name. The description adds no parameter 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?

States a specific verb and resource ('Add a straight line') plus the target container ('to a sketch'), which naturally separates it from sketch_arc, sketch_circle, and sketch_rectangle. It stops short of naming those siblings explicitly, so an agent still has to infer the routing.

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 prefer this over sketch_arc/sketch_circle/sketch_rectangle, no prerequisites such as whether the sketch must already exist or be active, and no notes on what to do afterwards. The agent is left to infer all usage context.

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