Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

get_entity

Retrieve detailed AutoCAD entity data by handle, including geometry, text, block attributes, length, and area, to inspect drawing objects for AI-driven editing or analysis.

Instructions

Подробно об объекте по handle: геометрия, текст, атрибуты блока, длина/площадь.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handle": "<handle>"
    },
    "name": "get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the categories of data returned (geometry, text, block attributes, length/area), which strongly implies a non-mutating lookup. However, it never explicitly states read-only behavior, what happens with an invalid or missing handle, or whether the entity must be in the active drawing.

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?

A single compact sentence with the resource and return contents front-loaded and zero redundant wording. Nothing in it is filler.

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?

The tool is simple (one required parameter) and has an output schema, so return values need no explanation; the description correctly focuses on saying what kinds of data come back. Only error/invalid-handle behavior and steering toward sibling tools are missing, which is a minor gap for a lookup tool.

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 description coverage is 0%, so the description must compensate for the single undocumented 'handle' parameter. Saying 'по handle' does establish that the handle identifies the target entity, but it adds no format, source (e.g., from drawing_summary or prior query results), or validity information.

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?

The description names a specific verb ('Подробно об объекте' — detailed info about an object) and resource (entity by handle), and enumerates what is returned: geometry, text, block attributes, length/area. It is clearly a read/inspect operation distinct from siblings like offset_entity, erase_entities, or drawing_summary, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance; the usage (pass a handle to inspect that entity) is only implied by the phrase 'по handle'. Nothing tells the agent whether to use this instead of drawing_summary or a broader listing, or what prerequisites a valid handle requires.

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