Skip to main content
Glama

cad_measure

Read-onlyIdempotent

Get distance between two points or calculate area/volume of a CAD object. Use for quick measurement queries in 2D/3D models.

Instructions

Measure a distance or an object's area/volume.

聚合测量操作。按 ``action`` 派发:distance / area。
- ``distance``: Euclidean distance between ``point_a`` and ``point_b``
  (2D ``[x, y]`` or 3D ``[x, y, z]``), returns ``distance``.
- ``area``: measure an existing object by ``object_id`` — 2D kinds
  (circle / rectangle / polygon) return area (``mm^2``), 3D kinds
  (box / cylinder / sphere / cone) return volume (``mm^3``); ``kind``
  in the output reports which.

When not to use: ``cad_measure`` reads existing geometry. To query
object position / bounding box use ``cad_object`` (action=read) or
``cad_status`` (target=object); to validate mesh validity use
``cad_validate`` (action=geometry).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
measureYesMeasurement to perform, discriminated by `action`: distance or area.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoMeasurement kind: area / volume
unitNomm^2 for area, mm^3 for volume
valueNoMeasured value
actionYesMeasurement action executed
statusYesOperation status
messageNoStatus description
distanceNoDistance between the two points
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable context beyond this: it notes the tool 'reads existing geometry', details that area action returns area for 2D kinds and volume for 3D kinds, and explains output includes a 'kind' field. This enhances understanding of the tool's behavior without contradicting annotations.

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 and front-loaded with a clear summary. Each section (action details, output semantics, alternatives) earns its place without unnecessary verbosity. The use of bullet points and 'When not to use' enhances readability and scannability.

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?

Given the tool's moderate complexity, the description covers all essential aspects: the two actions, parameter requirements, output behavior, and exclusions. Since an output schema exists, return values are documented elsewhere. The description is complete for an agent to select and invoke the tool correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds meaning by explaining how the 'action' parameter discriminates between the two measurement modes, the point format for distance, and the object_id usage for area/volume. It also clarifies the output units (mm^2, mm^3), which is not fully explicit in the schema.

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 clearly states the tool measures distance or an object's area/volume, with specific actions (distance/area) and differentiates from sibling tools like cad_object and cad_validate by specifying what it does not do. The verb 'measure' and resource (geometry) are explicit.

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?

The description provides explicit usage guidance, including a 'When not to use' section that names alternatives (cad_object, cad_status, cad_validate) for other queries. It also explains the action-based dispatch for distance vs area/volume, giving clear context for when each mode is appropriate.

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/Tianshang301/TianshangCAD'

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