Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

fillet

Rounds selected edges of the active part's first body in Autodesk Inventor by radius and edge indices; re-run find_edges before each call because edge numbers change after features.

Instructions

Round edges of the active part's first body. For an angled edge use chamfer; to round a profile's corners before extruding, use draw_closed_profile radii.

Edge numbers change after every feature: run find_edges again before the next fillet, and give all edges of one radius in one call. Tangent edges are followed automatically. Fails if the radius doesn't fit the geometry — fillet the big radii first. Returns the feature name.

Args: radius: Fillet radius in mm, e.g. 2. edge_indices: Comma-separated edge numbers from find_edges, e.g. "1,2,3".

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.8/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 well: it discloses that edge indices are invalidated by every feature, that tangent edges are followed automatically, that the operation fails when the radius exceeds the geometry, and the workaround (large radii first). It stops short of stating that this mutates the active document or what preconditions (an open part with an existing body) must hold, so it is strong but not complete.

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?

Front-loaded with the action, then routing to alternatives, then the critical edge-renumbering caveat, then failure behavior, then args. Every sentence carries non-obvious operational information; nothing is padding or restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the brief "Returns the feature name" is sufficient rather than a gap. Combined with the alternative routing, index-invalidation warning, and failure guidance, an agent has everything needed to invoke this correctly on the first try.

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 33% (only `instance` is documented inline), and the description compensates fully: radius is given a unit and example (mm, e.g. 2) and edge_indices is given format plus provenance (comma-separated numbers from find_edges, e.g. "1,2,3"). Both undocumented schema parameters gain meaning the schema alone does not convey.

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 opening sentence gives a specific verb and resource ("Round edges of the active part's first body") and immediately scopes it away from two siblings by name (chamfer for angled edges, draw_closed_profile radii for sketch corners). An agent can distinguish this from chamfer and the profile-drawing tools without opening any schema.

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?

It names explicit alternatives with the conditions that select them ("For an angled edge use chamfer", "to round a profile's corners before extruding, use draw_closed_profile radii") and states a hard sequencing rule (run find_edges again first because edge numbers change; batch all same-radius edges in one call). Both when-to-use and when-not-to-use are covered.

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