Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

list_entities

Retrieve AutoCAD model entities with handles, types, layers, colors, and bounding boxes. Filter by layer pattern, DXF entity type, rectangular area, crossing mode, or result limit.

Instructions

Список объектов модели с handle, типом, слоем, цветом и габаритом. Фильтр: layer (шаблон, напр. 'WALL*'), entity_type (тип DXF: LINE, LWPOLYLINE, CIRCLE, ARC, TEXT, MTEXT, DIMENSION, INSERT, HATCH...; через запятую), area [x1,y1,x2,y2] (целиком внутри; crossing=True: касается). limit: максимум в ответе.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
layerNo
limitNo
crossingNo
entity_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral load. It discloses filter semantics (area inside vs. crossing) and limit meaning, but omits whether the operation is read-only, how results are ordered, and whether pagination exists beyond a single limit.

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?

A single dense paragraph front-loads the core purpose and then details filters with examples. There is no redundant wording, though slightly more structure (e.g., separating filters) could improve scan-ability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 optional parameters, no annotations, and an output schema, the description covers parameter semantics well but lacks explicit usage guidance versus alternatives and omits read-only/pagination details. It is adequate but not fully complete for an agent to decide when to choose this tool.

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 coverage is 0%, so the description must supply parameter meaning. It defines layer as a pattern, entity_type as comma-separated DXF types with examples, area as a bounding box with crossing flag, and limit as maximum results. It adds substantial meaning beyond the bare schema, though default values and crossing-without-area behavior are left implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Список объектов модели' (list model entities) and enumerates returned fields (handle, type, layer, color, dimensions). No sibling differentiation is provided, so an agent cannot easily distinguish it from similar tools like select_entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains filter parameters but gives no explicit when-to-use or when-not-to-use guidance, and does not mention alternatives or exclusions. Usage is implied by the filter descriptions rather than stated.

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