Skip to main content
Glama

cad_validate

Read-onlyIdempotent

Detect geometric errors and interferences, inspect topology, and retrieve CAD document metrics for validation.

Instructions

Validate geometry, detect interference, inspect topology or fetch metrics.

聚合校验操作。按 ``action`` 派发:geometry / interference / topology / metrics。
- ``geometry``: check objects for self-intersections, degenerate faces and
  non-manifold edges (optional ``object_ids`` filter); returns issues with
  ``type`` / ``location`` / ``fix_suggestion``.
- ``interference``: detect box-box overlaps between objects, with overlap
  volume per pair.
- ``topology``: per-object vertex/edge/face counts and manifold status.
- ``metrics``: aggregate document stats (files, objects, layers, bbox,
  kinds) for the current session.

When not to use: ``cad_validate`` analyzes correctness and aggregates.
For simple geometric measurements (distance / area) use ``cad_measure``;
for live server/file/object status use ``cad_status``; for JSON scene
validation against the schema use ``cad_json`` (action=validate).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesValidation action to perform, discriminated by `action`: geometry, interference, topology or metrics.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxNoDocument bounding box
filesNoOpen files
kindsNoObject count by kind
pairsNoInterfering pairs
validNoWhether all checked objects are valid
actionYesValidation action executed
issuesNoDetected issues
layersNoTotal layers
statusYesOperation status
checkedNoNumber of objects checked
messageNoStatus description
objectsNoTotal objects
warningsNoTopology warnings
summariesNoPer-object topology
object_countNoNumber of objects
total_volumeNoSum of all overlap volumes
interference_countNoNumber of interfering pairs
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive behavior. The description adds per-action output semantics (e.g., issues with type/location/fix_suggestion, overlap volume, manifold status, aggregate metrics) which goes beyond annotations. Minor gap: doesn't mention error conditions or performance characteristics, but overall 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 well-structured with a one-line summary, detailed bullets per action, and a dedicated 'When not to use' section. Every part adds value; no redundant or filler content. The bilingual note is brief and harmless.

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 complexity as a four-action dispatcher, the description covers each action's purpose, key inputs, and output highlights. Combined with rich schema descriptions, an output schema, and clear annotations, the description is complete for selecting and invoking the tool correctly.

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 coverage is 100%, so the schema already documents the 'query' discriminator and 'object_ids' filter thoroughly. The description reinforces the action choices and mentions the optional object_ids filter, but doesn't add meaningful new parameter-level detail beyond what the schema provides. Baseline 3 applies.

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 validates geometry, detects interference, inspects topology, or fetches metrics. It explicitly enumerates the four actions and distinguishes itself from siblings in the 'When not to use' section, naming cad_measure, cad_status, and cad_json as alternatives for other use cases.

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?

Provides explicit guidance on when to use this tool versus alternatives. The 'When not to use' section names specific sibling tools for simple measurements, live status, and JSON validation, making the decision boundary very clear.

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