Skip to main content
Glama
ab7646

fusion-reconstruct-mcp

by ab7646

fusion_extrude

Extrude sketch profiles into 3D bodies, or modify existing ones using join, cut, or intersect operations with specified distance and taper.

Instructions

Extrude a sketch profile.

operation: "new_body" | "join" | "cut" | "intersect". "join"/"cut"/ "intersect" combine into target_body_id (required for those three).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNonew_body
sketch_idYes
symmetricNo
distance_mmYes
profile_indexYes
target_body_idNo
taper_angle_degNo
Behavior3/5

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

The description discloses a key behavioral trait: 'join'/'cut'/'intersect' combine into target_body_id and require it. However, it does not mention side effects like timeline impact, body mutation, or return values. With no annotations, the description carries the full burden and only partially fulfills it.

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 compact, front-loaded, and free of filler. It conveys the core purpose and a critical parameter constraint in just two sentences.

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 has 7 parameters, no annotations, no output schema, and no parameter descriptions in the schema. The description covers only operation and target_body_id, omitting essential meaning for the required parameters and other options. This is incomplete for safe and correct invocation.

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 description explains the operation enum values and the conditional requirement for target_body_id, but it leaves sketch_id, profile_index, distance_mm, symmetric, and taper_angle_deg completely unexplained. Since schema description coverage is 0%, this is a significant 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?

The description starts with 'Extrude a sketch profile,' which is a specific verb+resource that clearly distinguishes this tool from siblings like fusion_revolve and fusion_loft. It also lists the operation variants, adding precision.

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?

No guidance is given on when to use extrude versus alternative operations. The description does not mention prerequisites, typical use cases, or situations where another tool would be more appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ab7646/fusion-reconstruct-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server