Skip to main content
Glama
maximedns5

freecad-mcp

by maximedns5

sweep

Create curved parts by moving a profile along a path, producing bends, pipes, and ribs that standard operations cannot achieve, with support for arcs and splines.

Instructions

Run a profile along a path — genuinely curved parts.

This is how you get curvature that pad/pocket/loft cannot express: a
shaft that bends, a pipe, a curved rib, a hose. The path can be any
wire, including an arc or spline, so the result follows a real curve
rather than a series of straight segments.

`frenet=True` keeps the profile's orientation consistent along the
path, which is what you want for a bent shaft; the alternative can
twist the section unpredictably.

Args:
    doc_name: The document.
    name: Name for the resulting swept solid.
    profile: Name of the profile object to sweep (a sketch or face).
    path: Name of the path object (a wire, arc, or spline) to follow.
    solid: Produce a solid rather than a surface.
    frenet: Keep the profile orientation consistent along the path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
pathYes
solidNo
frenetNo
profileYes
doc_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the burden of explaining behavior. It discloses the effect of the frenet parameter, noting it 'keeps the profile's orientation consistent' and that the alternative 'can twist the section unpredictably.' It also implies solid vs. surface but does not explicitly state whether the tool mutates the document or creates a new object, which is a minor omission.

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 well-structured with an opening summary, explanatory paragraph, and a clear Args list. Every sentence provides useful information—there's no fluff or repetition. The length is justified by the complexity of the operation.

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?

Given the presence of an output schema, the description needn't detail return values. It covers purpose, usage, parameter semantics, and critical behavioral nuances (frenet twist). It is complete enough for an agent to select and invoke sweep correctly, especially with sibling tools like pad and pocket available for contrast.

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 description coverage is 0%, but the description fully compensates by defining each parameter in the Args block: profile ('a sketch or face'), path ('a wire, arc, or spline'), solid ('Produce a solid rather than a surface'), and frenet ('Keep the profile orientation consistent'). This adds meaning the schema lacks, so the tool is easy to invoke correctly.

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 opens with 'Run a profile along a path — genuinely curved parts,' which clearly states the action and resource. It explicitly differentiates from pad/pocket/loft by noting that sweep is for bends or curves those operations cannot express, such as a bent shaft or pipe.

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 explicitly states when to use this tool: 'This is how you get curvature that pad/pocket/loft cannot express,' and gives concrete examples like a shaft, pipe, curved rib, or hose. It also clarifies that the path can be an arc or spline, providing clear guidance versus alternatives.

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/maximedns5/freecad-mcp'

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