Skip to main content
Glama

list_dimensions

Lists every dimension in the active document with exact path, value, and units to map spoken edits to the correct dimension for conversational CAD modification.

Instructions

Descubre qué dimensión mover — lista TODAS las cotas del documento activo.

El paso de descubrimiento para edición conversacional ("hazlo 5mm más largo", "cambia el barreno a Ø8"): enumera cada dimensión alcanzable — de operaciones Y de croquis — con su path exacto ("D1@Saliente-Extruir1"), valor actual y unidades. Para mapear lenguaje a la cota correcta, cruza el VALOR hablado con los valores listados (el largo de 80 → la cota que vale 80); en empate, desambigua por owner_type o pregunta. Luego pasa owner/name verbatim a modify_dimension. Read-only.

Returns: {count, dimensions: [{path, owner, owner_type, name, value, units("mm"|"deg")}]}. Con un ensamble activo lista las cotas de mates (D1 de distance/angle; owner_type "mate_distance"/"mate_angle") — las cotas internas de componentes requieren abrir la pieza. Caveat (COM): cotas renombradas fuera de D1..Dn no aparecen; una cota angular de croquis se reporta como longitud en mm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavior: lists all dimensions from operations and sketches, includes assembly mate dimensions in active assembly, notes internal component dimensions require opening the part, and highlights caveats about renamed dimensions and angular sketch dimension reporting.

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?

Well-structured with clear paragraphs, front-loaded purpose, and no redundant sentences. Could be slightly more concise, but overall efficient for the amount of information conveyed.

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?

Fully describes return format with structured details, explains behavior in different contexts (assembly vs part), and covers edge cases. No output schema, but description compensates completely.

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?

No parameters exist, so schema coverage is 100% vacuously. Baseline is 4 per guidelines. The description does not need to add parameter info but provides context about the tool's function.

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?

Description clearly states the tool lists all dimensions from the active document, specifying it includes operations and sketches with exact path, value, and units. It differentiates from siblings like modify_dimension and add_sketch_dimension by framing it as a discovery step for conversational editing.

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 (discovery step before modification), provides precise instructions for mapping spoken values to dimensions, and mentions to pass results verbatim to modify_dimension. Also notes it is read-only, giving clear context for usage.

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/danielproxd2/MCP_CAD'

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