Skip to main content
Glama
U-C4N
by U-C4N

Measure Area

analysis_measure_area
Read-onlyIdempotent

Compute the area and perimeter of a polygon from vertex coordinates, including curved edges via bulge values, for accurate measurements.

Instructions

Area and perimeter of a polygon you supply the vertices for.

This measures the numbers in the call, NOT the drawing. To measure something that exists, use analysis_measure_entity(handle) — it reads the real geometry, including curvature this tool can only see if you pass it.

Straight-edged polygons are exact. Pass a third bulge element per vertex for arc edges; omitting it on curved geometry under-reports (28% on a semicircular edge), which is why assumes says what was taken on faith.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYesPolygon vertices, min 3. Each is [x, y] or [x, y, bulge] — the bulge (DXF convention) makes the edge leaving that vertex a circular arc.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Adds substantial context beyond annotations: it describes the non-drawing nature, the bulge parameter effect, exactness for straight edges, and a specific under-reporting example (28% on a semicircular edge). It also mentions `assumes` to convey what is taken on faith. No contradiction with readOnly/idempotent hints.

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 three concise paragraphs: clear function statement, comparison to alternative, and accuracy caveats. Every sentence adds value, with no fluff or repetition.

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?

Covers purpose, usage, limitations, parameter semantics, and alternative tool. The tool is simple (one parameter) and the description is sufficiently complete for an agent to select and invoke it correctly, especially with output schema and annotations present.

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 description enriches the schema's `points` parameter by explaining the bulge (DXF convention), arc edge behavior, and warns about omitting bulge on curved geometry. This goes well beyond the basic schema definition.

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 a specific verb+resource: 'Area and perimeter of a polygon you supply the vertices for.' It clearly distinguishes from `analysis_measure_entity` by stating this tool measures the numbers in the call, not the drawing.

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?

Explicitly states when to use this tool vs. the alternative: 'To measure something that exists, use analysis_measure_entity(handle)...' and clarifies that this tool is for supplied vertices, not existing geometry.

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/U-C4N/Autocad-MCP'

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