Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

partdesign_sweep

Create additive or subtractive PartDesign features by sweeping a profile sketch along a spine path; changes are undoable.

Instructions

Sweep a profile Sketch along a spine path (AdditivePipe or SubtractivePipe) (undoable).

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": {
      "profile_name": "<profile_name>",
      "spine_name": "<spine_name>"
    },
    "name": "partdesign_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
doc_nameNo
spine_nameYes
orientationNoStandard
subtractiveNo
profile_nameYes
spine_subelementsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation/safety profile is largely covered. The description adds useful context beyond that by stating the operation is '(undoable)', telling the agent a failed or unwanted sweep can be reverted. It does not explain what the subtractive mode actually removes or what happens to existing features, which would have raised the score.

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?

One sentence, front-loaded with the core action and parenthetical clarifications kept short. No redundant wording, though the terseness comes at the cost of parameter and usage detail rather than being purely a structural weakness.

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?

This is a mutation tool with seven parameters, none documented in the schema, and no annotations covering permissions or side effects; only the return format is offloaded to the output schema. Given that complexity, the one-line description leaves too much (orientation, subelements, document targeting, failure modes) unspecified.

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?

Schema description coverage is 0% across seven parameters, so the description must carry the semantic load, but it only hints at profile_name, spine_name, and the additive/subtractive choice. Parameters like doc_name, name, orientation (default 'Standard'), and spine_subelements receive no explanation anywhere, leaving half the surface undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource: 'Sweep a profile Sketch along a spine path', and identifies the underlying operations (AdditivePipe or SubtractivePipe). It does not differentiate itself from related siblings such as partdesign_loft or partdesign_revolution, so an agent must already know the modeling distinction.

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

Usage Guidelines3/5

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

Mentions both modes of the operation (AdditivePipe or SubtractivePipe), which implicitly maps to the 'subtractive' parameter, so the agent can infer the union vs. cut choice. However, there is no explicit when-to-use guidance versus loft/revolution, no prerequisites (e.g., profile must be a sketch, spine must exist), and no statement of what to do when the profile or spine is invalid.

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