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

partdesign_revolution

Revolve a sketch around an axis to add solid material in PartDesign, with angle, midplane, and reverse options for controlled, undoable modeling.

Instructions

Revolve a Sketch around an axis to add solid material in PartDesign (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": {
      "sketch_name": "<sketch_name>"
    },
    "name": "partdesign_revolution"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNoV_Axis
nameNo
angleNo
doc_nameNo
midplaneNo
reversedNo
sketch_nameYes

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, non-idempotent and closed-world behavior, so the safety profile is largely covered. The description adds one genuinely useful piece of context, '(undoable)', which is not expressed in the annotations. However it says nothing about failure modes, required active body, or whether re-invoking with identical arguments creates duplicate features — a relevant gap given idempotentHint=false.

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?

A single tight sentence with the verb-plus-resource front-loaded and no filler. It is appropriately short, though the terseness is partly the cause of the parameter and prerequisite gaps rather than a sign of full specification.

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?

Return values are covered by the output schema, so that is not a gap. But for a 7-parameter modeling operation with zero schema description coverage, the definition omits everything an agent needs about angle units, axis selection format, midplane/reversed semantics, and body prerequisites, leaving a substantial shortfall relative to tool complexity.

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 7 parameters, so the description carries the full burden and largely fails it. Only 'sketch' and 'axis' are touched obliquely by the prose; angle (default 360), midplane, reversed, doc_name and name are given no meaning at all, and no defaults or units are restated.

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?

States a specific verb and resource (revolve a sketch around an axis) and adds the effect (adds solid material) plus the workbench context (PartDesign). The phrase 'add solid material' implicitly distinguishes it from the subtraction counterpart partdesign_groove, though no sibling is named explicitly.

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?

Usage is only implied: the agent must infer that this is the additive revolution operation and that a sketch must already exist in an active body. There is no explicit when-to-use, no mention of groove as the subtractive alternative, and no stated prerequisites such as an active body or a valid axis selection.

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