Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

chamfer

Adds an equal-distance bevel to selected edges of the active part's first body, accepting all edge numbers in one call so later features do not target wrong edges.

Instructions

Add an equal-distance chamfer to edges of the active part's first body. For rounded edges use fillet; on sheet metal corners, add_corner_round.

Give ALL edges in one call: edge numbers change after every feature, so a second call with old numbers hits the wrong edges. Returns the feature name.

Args: distance: Chamfer distance 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": "chamfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
distanceNo
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.5/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 so well: it discloses the mutation target (active part's first body), the critical side effect that edge numbering becomes stale after each feature, and the return value ('Returns the feature name'). It stops short of covering failure modes (invalid indices, no active document) or any preconditions on the distance value, so a 4 rather than a 5.

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?

Front-loaded: capability and scope land in sentence one, sibling routing in sentence two, and the batching warning before the args block. The Args section slightly restates the schema's shape but justifies itself with units, formats, and source provenance, so almost nothing is wasted.

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 little explanation, and the description still notes the returned feature name. Together with the edge-index batching warning and the documented edge/distance formats, an agent has enough to call this correctly; only the undocumented 'instance' param and absent error behavior keep it from a 5.

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

Parameters4/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 in-schema — so the description must compensate, and it does for two of three params: it gives units and an example for 'distance' ('in mm, e.g. 2') and provenance plus format for 'edge_indices' ('Comma-separated edge numbers from find_edges, e.g. "1,2,3"'). The 'instance' parameter is left entirely to the schema description, which is a minor remaining gap.

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 and resource ('Add an equal-distance chamfer') plus an explicit scope ('edges of the active part's first body'). It also names the two siblings it must not be confused with (fillet for rounded edges, add_corner_round for sheet metal corners), making it unambiguously distinguishable.

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?

Gives explicit routing rules to alternatives ('For rounded edges use fillet; on sheet metal corners, add_corner_round') and a batching rule with a stated failure consequence ('Give ALL edges in one call... a second call with old numbers hits the wrong edges'). When-to-use, when-to-use-something-else, and how to sequence are all covered.

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