Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

check_sketch

Read-only

Diagnose why a sketch fails to extrude or revolve by detecting open ends, gaps, overlaps, and duplicate lines, then report whether Inventor builds a closed profile and loop count.

Instructions

Why won't it extrude? Checks a sketch for what a closed profile needs: open ends, gaps (two ends a hair apart, not joined), points where 3+ curves meet (overlaps, stray lines), lines drawn twice — with sketch coordinates in mm — and whether Inventor builds a profile, with how many closed loops. extrude / revolve report the same when they fail.

Args: 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": "check_sketch"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond that — reporting coordinates in mm and whether a profile is built plus loop count — but with an output schema present, much of the return-value burden is already handled elsewhere, making this a moderate rather than rich contribution.

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?

The description is front-loaded with the failing scenario and then the diagnostic categories, which is efficient. A few phrasings are wordy ('two ends a hair apart, not joined', 'lines drawn twice'), but they clarify rather than pad, and nothing extraneous is included.

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 read-only diagnostic with an output schema handling return structure, the description covers the failure conditions it detects and the profile/loop verdict it produces. The only real gap is the thin documentation of sketch_index beyond '0 = latest sketch', which is acceptable given the low parameter count.

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 only 50%: the instance parameter is documented in the schema while sketch_index is not. The description compensates partially by documenting 'sketch_index: Sketch number (0 = latest sketch)', which adds the meaning of the default value. That recovers some of the gap but does not fully document the parameter's range or behavior.

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?

The description leads with the concrete problem ('Why won't it extrude?') and states a specific verb and resource: it checks a sketch for the conditions a closed profile requires. It enumerates the exact failure classes (open ends, hairline gaps, 3+ curve junctions, duplicate lines) and says it also reports whether Inventor builds a profile and how many closed loops, which distinguishes it from siblings like extrude or revolve.

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?

Usage context is clear: it is the diagnostic to reach for when extrude or revolve fail, and the note that 'extrude / revolve report the same when they fail' tells the agent these tools surface the same info on failure. It does not explicitly state when not to use it or name a distinct alternative for other sketch problems, so it stops short of full when/when-not guidance.

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