Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

draw_line

Draws one straight line in a sketch, either open or as a construction line for a revolve axis. Use for individual lines that do not form a closed profile.

Instructions

Draw one straight line in a sketch, in the sketch's coordinates — an open line, or a construction line for a revolve axis. Lines drawn one by one don't join into a profile: for a closed shape use draw_closed_profile or draw_rectangle.

Args: x1: Start X in mm. y1: Start Y in mm. x2: End X in mm. y2: End Y in mm. sketch_index: Sketch number (0 = latest sketch). construction: If True, line becomes a construction line (used as revolve axis, not part of profile).

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

Input Schema

NameRequiredDescriptionDefault
x1No
x2No
y1No
y2No
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
constructionNo
sketch_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the coordinate system, the fact that segments don't auto-join into profiles, and the semantic difference of construction lines (used as revolve axis, excluded from profile). It does not mention prerequisites such as needing an active document/sketch or connected instance, which for a mutating tool would be useful.

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 key behavioral constraint (no profile joining, use draw_closed_profile instead) is front-loaded before the Args block, and each parameter line is a single informative clause. No filler sentences.

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 7-param sketching tool with an output schema, the description covers geometry, units, construction semantics, and sibling routing. It stops short of stating preconditions (active document, connection via instance) or what the return actually confirms, but the output schema covers return values.

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 coverage is only 14%, but the description compensates by documenting six of the seven parameters with units (mm), meaning, and semantics (sketch_index 0 = latest sketch; construction = revolve axis, not part of profile). The only undocumented-in-description parameter, instance, already has a schema description, so nothing is left ambiguous.

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?

States a specific verb+resource ("Draw one straight line in a sketch") plus scope (open line vs. construction line for a revolve axis). It actively distinguishes itself from siblings by naming draw_closed_profile and draw_rectangle as the tools for closed shapes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when NOT to use it ("Lines drawn one by one don't join into a profile") and names the alternatives for that case. Also states the condition for the construction flag, so both usage paths are covered.

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