Skip to main content
Glama
tomo1230

FreeCAD MCP Server

by tomo1230

copy_body_symmetric

Creates a symmetric copy of a body mirrored across a selected plane (xy, xz, or yz).

Instructions

FreeCAD tool: copy_body_symmetric

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_body_nameNoBody name
new_body_nameNoBody name
planeNoxy|xz|yzxy
Behavior1/5

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

No annotations are provided, and the description gives no behavioral traits. It does not disclose whether the operation is destructive, if it requires certain permissions, or any side effects. The agent has no insight into the tool's behavior beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only one line but it is not effective. It lacks substance and fails to convey the tool's purpose. It is under-specified rather than concise, providing no meaningful information.

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

Completeness1/5

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

Given the tool's complexity (a FreeCAD operation for copying a body symmetrically), the description is extremely incomplete. No output schema exists, and the description does not explain return values, prerequisites, or effects. The agent cannot determine what will happen or what is needed.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter having a brief description in the schema (e.g., 'Body name' for source_body_name and new_body_name, 'xy|xz|yz' for plane). The tool description adds no additional meaning. Since the schema already provides basic parameter info, a baseline of 3 is appropriate.

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

Purpose2/5

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

The description 'FreeCAD tool: copy_body_symmetric' essentially restates the tool name without explaining what the tool does. It fails to specify the action (copying) or the resource (body) in a meaningful way. The purpose is vaguely implied by the name but not clarified.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, conditions, or when not to use it. This leaves the agent without context for appropriate invocation.

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/tomo1230/freecad_mcp_server'

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