Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

list_profiles

Retrieve profile catalog data—article, purpose, depth, and Ix—to select structural and window/door components for AutoCAD drawings.

Instructions

Каталог профилей: артикул, назначение (стойка/ригель/стропило/рама/импост/створка/прижим/крышка), глубина, Ix см4.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it implies a read-only catalog but never says so explicitly, nor whether the catalog is static/library-backed or drawing-scoped. It does add useful content detail by spelling out the 'назначение' categories (стойка/ригель/стропило/рама/импост/створка/прижим/крышка), which is genuine behavioral context beyond structured fields.

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 compact line with the resource front-loaded and the field list trailing; nothing is padded. It is arguably over-terse for an agent needing selection guidance, but no sentence is wasted.

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 zero parameters and an output schema present, the description need not explain return values, and it covers the catalog's domain fields adequately. What is missing is scope and intent: whether this lists an available section library for later draw_walls/draw_* use, and whether results are fixed or filtered.

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 the schema needs no parameter explanation and the baseline is 4. The description correctly spends no words on arguments and instead describes the returned catalog content.

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?

Names the resource precisely ('Каталог профилей') and enumerates the attributes it exposes (артикул, назначение, глубина, Ix см4), so an agent knows this returns profile-catalog entries rather than drawing objects. It lacks an explicit verb and never contrasts itself with the list_* siblings, which keeps it short of a 5.

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 statement of when to call this versus the sibling list tools (list_blocks, list_entities, list_layers) or when a profile lookup is the right step before a draw_* call. The only usage signal is implicit in the word 'каталог'.

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