Skip to main content
Glama
maximedns5

freecad-mcp

by maximedns5

add_polygon

Create custom closed polygon shapes in a FreeCAD sketch from a list of [x, y] points. Connects points in order and auto-closes the loop, ideal for L, T, hexagon outlines.

Instructions

Add a fully-constrained closed polygon to a sketch from [x, y] points.

This is the only way to express an L, T, hexagon, or other custom
outline. Points are connected in order and the loop closes automatically
(do not repeat the first point at the end).

Args:
    doc_name: The name of the document.
    sketch_name: The name of the sketch to add geometry to.
    points: List of [x, y] points in sketch-local space, at least 3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes
doc_nameYes
sketch_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 full burden and discloses important traits: points are connected in order, loop closes automatically, coordinates are in sketch-local space, and the resulting polygon is fully-constrained. It does not cover failure modes or side effects, but the core behavior is transparent.

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 and front-loaded: the first sentence states the main purpose, the second adds key behavioral distinctions, and the Args list gives precise parameter semantics without redundancy.

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

Completeness4/5

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

The tool has a straightforward parameter set and an output schema, so the description covers the essential usage, coordinate system, auto-close behavior, and shape-specific use case. It omits prerequisites (e.g., that the document/sketch must already exist), but overall it is sufficiently complete for an agent to invoke it.

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?

The input schema provides no parameter descriptions (0% coverage), but the description's Args section fully explains all three parameters, including the points format ('[x, y]' in sketch-local space) and the minimum count of 3.

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 uses a specific verb ('Add') and resource ('fully-constrained closed polygon to a sketch from [x, y] points'), and explicitly differentiates from sibling tools by stating it is the only way to express L, T, hexagon, or custom outlines.

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

Usage Guidelines4/5

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

It clearly communicates when to use the tool ('only way to express an L, T, hexagon, or other custom outline'), giving strong contextual guidance, but it does not name specific alternatives or state explicit when-not scenarios.

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