Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

acad_status

Check the active engine and AutoCAD connection status, identify the current drawing file, and report the object count.

Instructions

Статус: активный движок, подключён ли AutoCAD, текущий файл, число объектов.

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": "acad_status"
  }
}

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 supplied, so the description carries the full burden. It discloses the fields reported, which implies a non-mutating query, but says nothing about behavior when AutoCAD is not connected (error vs. status flag) or whether calling it has any side effects. Adequate but thin for a tool with zero annotation coverage.

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 front-loaded sentence with a colon and a compact field list; no filler, no repetition of the tool name. Every word contributes 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?

With zero parameters and an output schema present, the description does not need to explain return values, and the tool's simplicity means little else is required. The only real omission is the connection-failure behavior, which is a minor gap for a status probe.

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 no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter discussion.

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 the resource (status) and enumerates exactly what it reports: active engine, AutoCAD connection state, current file, and object count. That is specific enough for an agent to know this is a read-only environment/diagnostic probe rather than a drawing or entity tool. It stops short of explicitly distinguishing itself from the similarly-scoped 'drawing_summary' sibling.

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 statement, no mention of calling it before draw operations to verify the AutoCAD connection, and no exclusion of alternatives. The agent must infer the usage pattern entirely from the word 'Статус'.

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