CADPilot

Overview Schema Source Related Servers Discussions Admin

get_topology

Read-onlyIdempotent

List a CAD object's faces, edges, or vertices sorted by area, length, or distance to select geometry for fillets, booleans, or sketches.

Instructions

List an object's topology for selection: faces by area, edges by length, vertices by distance, largest first. The names (Face1, Edge3, ...) feed fillet, boolean, sketch-on-face and friends.

Args:
    element: Which kind to list: faces, edges or vertices.
    limit: Max entries (1 to 200, default 50).
    offset: How many entries to skip.

Returns: total, returned, and a '{element}' list of {index, name, type, area or length, center, planar-face normal}.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`offset`	No
`element`	No	faces
`doc_name`	Yes
`obj_name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.7Oct 7, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +200
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / offset / maximum
```
Added value: +10000000
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
First observedv0.4.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds real behavioral value on top with the 'largest first' sort order and the fact that pagination exists. It does not discuss error behavior or what happens when an object has no topology, which keeps it below 5.

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

Conciseness4/5

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

Front-loaded with the purpose and ordering before the Args/Returns blocks, and every line earns its place. The Args block partly restates schema defaults/ranges, which is mild redundancy but aids readability rather than bloating the definition.

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?

For a read-only, paginated listing tool, the definition covers ordering, pagination controls, the shape of the result and the downstream purpose of the returned names. The only gaps are edge-case behavior (invalid element, empty topology) and any explanation of doc_name/obj_name scoping.

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 0%, so the description must carry the load, and it documents the three non-obvious parameters: element (faces/edges/vertices), limit (1–200, default 50) and offset (skip count). doc_name and obj_name are left undocumented, but their meaning is self-evident from the names and required-parameter list.

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?

States a specific verb and resource ('List an object's topology') plus the exact sub-entities covered (faces by area, edges by length, vertices by distance) and their ordering. This clearly separates it from siblings like get_objects (whole objects) and measure_geometry (measurements), so an agent can pick it without opening the schema.

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?

Gives a concrete use context: 'for selection', with the returned names feeding fillet, boolean and sketch-on-face operations. That tells the agent when the tool is appropriate, but it offers no explicit when-not or named alternative for topology-like queries, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.