fusion-reconstruct-mcp

Overview Schema Source Related Servers Discussions Admin

fusion_revolve

Revolve a selected sketch profile around a defined axis to create a parametric 3D body. Specify axis endpoints and angle to control the revolve feature.

Instructions

Revolve a sketch profile around an axis line given by two 2D points in the sketch's own coordinate system (mm).

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_id": "<sketch_id>",
      "profile_index": "<profile_index>",
      "axis_start": "<axis_start>",
      "axis_end": "<axis_end>"
    },
    "name": "fusion_revolve"
  }
}

Input Schema

Name	Required	Default
`axis_end`	Yes
`angle_deg`	No
`operation`	No	new_body
`sketch_id`	Yes
`axis_start`	Yes
`profile_index`	Yes
`target_body_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description is the sole source of behavioral information. It does not mention side effects (e.g., whether it modifies the document), potential errors (invalid profile, degenerate axis), or the nature of the operation (e.g., whether it creates a new body or cuts). The available parameters (operation, target_body_id) hint at such behaviors, but the description does not elaborate.

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 description is a single, concise sentence that conveys the core functionality without extraneous words. It is well-structured and easy to read, with no redundancy or ambiguity in phrasing.

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

Completeness2/5

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

The tool is moderately complex, involving a revolve operation with multiple parameters (angle, operation, target body). The description only covers the basic revolve action and axis definition, omitting details about how parameters affect the outcome, what the operation does (e.g., cut vs. join), and what the tool returns. Without additional context, a user may not fully understand how to use the tool correctly.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides parameter names but no descriptions. The description adds some context for axis_start and axis_end (two 2D points in the sketch's coordinate system) and mentions units (mm), but it does not explain other parameters like profile_index, angle_deg, operation, or target_body_id. Since schema coverage is 0%, the description should compensate more, but it only partially clarifies the axis parameters.

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 clearly states the tool's function: revolving a sketch profile around an axis defined by two points in the sketch's coordinate system. It uses a specific verb ('Revolve') and specifies the resource ('sketch profile') and the axis definition, distinguishing it from other modeling tools like extrusion or loft.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool over alternatives. It lacks context such as prerequisites (e.g., needing a valid sketch with a closed profile), typical use cases, or comparison with similar tools like fusion_extrude. Users are left to infer when a revolve is appropriate.

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