Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

loft

Blend closed sketch profiles on different planes to create transitions such as rectangle-to-circle ducts or tapered bosses, returning the feature name and volume/topology change.

Instructions

Blend between the closed profiles of two or more sketches on different planes — a rectangle-to-circle transition, a duct, a tapered boss. For a constant profile along a curve use sweep; for a straight push, extrude.

Put each section in its own sketch (create_sketch with offset gives parallel planes). Returns the feature name and the volume / topology change.

Args: sketch_indices: Comma-separated sketch numbers in the order to blend, e.g. "1,2,3". operation: "join" (add), "cut", "intersect" or "new" (a separate body). closed: Also blend the last section back into the first (a ring).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sketch_indices": "<sketch_indices>"
    },
    "name": "loft"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return value (feature name and volume/topology change), explains what each operation mode does to the model (join adds, cut removes, intersect, new creates a separate body), and states the sketch-plane precondition. It does not mention document-mutation irreversibility or instance targeting, leaving a small gap.

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 with purpose, then alternatives, then the sketch precondition, then an Args block — well organized and free of filler. The returns sentence partially duplicates the available output schema, a minor redundancy.

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 4-parameter geometry operation with no annotations, the definition covers purpose, alternatives, prerequisites, and parameter semantics, and an output schema exists so return values need not be detailed. Only the instance parameter and mutation behavior are unaddressed, which is minor given the schema covers instance.

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 25% (just 'instance'), so the description must compensate and largely does: it gives the comma-separated ordering format for sketch_indices, the meaning of each operation value, and what closed does. The instance parameter is left entirely to the schema, which is the one 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 (blend closed profiles of two or more sketches on different planes) plus concrete examples (rectangle-to-circle, duct, tapered boss). It explicitly distinguishes itself from sweep and extrude, so an agent can select it without opening sibling schemas.

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?

Gives explicit routing rules — use sweep for a constant profile along a curve, extrude for a straight push — and a prerequisite ('put each section in its own sketch, create_sketch with offset gives parallel planes'). Lacks explicit when-not/no-op conditions, but the alternative routing is clear.

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