Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

project_edges

Projects a body's edges onto a sketch as model-linked lines, arcs, circles, and splines so you can build from existing or imported geometry without retracing curves.

Instructions

Project a body's edges onto the sketch — exact lines, arcs, circles and splines, linked to the model. Use it to build on existing or reference geometry (e.g. remodelling an imported part) instead of re-tracing curves point by point.

Args: face_index: Project every edge of this face of the body (find_faces). edge_indices: Or these edges, "3,7,8" (find_edges). body_index: Body in a multi-body part (1 = first). sketch_index: Sketch number (0 = latest sketch).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_edges"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
body_indexNo
face_indexNo
edge_indicesNo
sketch_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a genuinely useful behavioral trait, that projected geometry stays 'linked to the model' (associative), but omits prerequisites such as whether an active/existing sketch is required, what happens when both face_index and edge_indices are supplied, and whether the operation is undoable.

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?

The purpose and the importable-geometry rationale are front-loaded in the first two sentences, followed by a compact args block where every line adds semantics rather than restating the schema. No filler.

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?

An output schema exists, so return values need not be explained, and the parameter explanations are thorough. The remaining gap is environmental: the definition never states that a target sketch must already exist and be active, nor how face_index and edge_indices interact when both are provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description must compensate, and it does: it explains each of the four core parameters with meaning beyond the schema, including cross-references to find_faces and find_edges, the "3,7,8" string format for edge_indices, 1-based body indexing, and sketch_index 0 = latest sketch.

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 description names a specific verb (project) and resources (a body's edges onto the sketch), and enumerates the resulting entity types (lines, arcs, circles, splines). It distinguishes itself from the draw_*/offset_profile family by emphasizing the result is 'linked to the model', though it doesn't name a specific sibling tool it competes with.

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?

It gives an explicit use case (building on existing or reference geometry, e.g. remodelling an imported part) and names the alternative practice it replaces ('instead of re-tracing curves point by point'). No when-not-to-use or prerequisite conditions are stated.

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