Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_point

Draws a POINT entity at specified X and Y coordinates in an AutoCAD drawing, optionally on a chosen layer.

Instructions

Точка (POINT) в (x,y).

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "draw_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
layerNo0

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: not whether the point is created on the current layer, how the optional layer default behaves, which coordinate system (WCS/UCS) is used, or whether the operation is undoable. Only the essential geometry (x,y) is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words and the key information is front-loaded, but the brevity comes from under-specification rather than efficient wording. It reads as a fragment rather than a complete instruction.

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

Completeness2/5

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

Because an output schema exists, return values need not be explained, but for a drawing-mutation tool with three parameters and no annotations the description should at least cover the layer parameter, coordinate expectations, and units. Those gaps leave the agent guessing how the call will affect the drawing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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. It explains x and y only as a coordinate pair and says nothing about the third parameter, layer, or its default of "0", leaving the agent without meaning for a third of the inputs.

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

Purpose3/5

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

"Точка (POINT) в (x,y)" identifies the resource (a POINT entity) and its coordinates, so the intent is inferable, but there is no verb and no explicit statement of what happens (creating a point in the current drawing). It is distinguishable from draw_circle/draw_line only by the entity type named, not by any stated scope.

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 guidance, no mention of alternatives such as draw_batch or draw_construction, and no prerequisites. The agent must guess whether this is the right tool for placing a single marker versus a batch.

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