Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

list_layers

Lists drawing layers with color, on/frozen/locked state, linetype, and current layer status so you can inspect layer settings before editing or generating CAD content.

Instructions

Список слоёв: цвет, вкл/заморожен/заблокирован, тип линии, текущий.

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_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 carries the full disclosure burden. It does reveal what attributes come back, which implicitly signals a read-only, non-mutating operation, but it says nothing about scope (which drawing/document the layers belong to), ordering, or empty-result behavior.

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 clause, front-loaded with the action and followed by the returned fields. No filler, no restatement of the tool name beyond what is needed, and every element adds information.

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 a simple zero-parameter read, and an output schema exists, so return values need no prose explanation. The description is close to complete for this complexity; only the scope of the layer list (active document) is left unstated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a 0-param tool applies. The description's field list is about output, not input, and does not confuse the two.

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 layers) and enumerates the attributes returned: color, on/frozen/locked state, linetype, and current-layer flag. An agent can distinguish this from create_layer/delete_layer by the verb alone, though no explicit sibling differentiation is written.

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?

Gives no when-to-use or when-not-to-use guidance, and never names an alternative such as list_entities or drawing_summary. Usage is only implied by the verb 'list' — it lists layers. An agent must infer that this is the pre-check before create_layer/delete_layer.

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