Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_hatch

Create hatching or solid fills for closed contours using point sets or a closed polyline, circle, or ellipse handle, with pattern, scale, angle, and color controls.

Instructions

Штриховка или заливка замкнутого контура: points [[x,y],...] или handle замкнутой полилинии/окружности/эллипса. pattern: ANSI31, ANSI37, AR-CONC, AR-B816, BRICK, GRAVEL, NET... или SOLID (заливка); scale: масштаб узора (для мм-чертежей обычно 10-50), angle: градусы, color: ACI.

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

Input Schema

NameRequiredDescriptionDefault
angleNo
colorNo
layerNoHATCH
scaleNo
handleNo
pointsNo
patternNoANSI31

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/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 does disclose useful operational heuristics (scale typically 10–50 for mm drawings, angle in degrees, color in ACI, SOLID means solid fill), but it says nothing about permissions, what happens with an unclosed or invalid contour, which layer is used by default, or that a new entity is created rather than modifying an existing one.

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 dense sentence, front-loaded with the core action and then the parameters, with zero filler. It is somewhat run-on and compressed, but every clause carries information the agent needs.

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

Completeness5/5

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

For a 7-parameter mutation tool with no annotations and no schema descriptions, the description covers nearly everything needed to call it correctly, and an output schema exists so return values need not be explained. Only the layer parameter is left to the schema.

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?

Schema description coverage is 0% across 7 parameters, so the description must compensate, and it mostly does: it explains points vs handle, gives concrete pattern names and the SOLID special case, supplies a practical scale range, and fixes the units for angle and color. The main gap is the layer parameter, which is never mentioned.

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 — hatching/fill of a closed contour — and enumerates the two ways to define that contour (points list or entity handle). It is unambiguous against siblings like draw_line or draw_polygon, though it never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

The 'замкнутый контур' (closed contour) constraint is a genuine usage precondition, and the points-or-handle phrasing implies the choice of input method. However there is no explicit when-to-use / when-not guidance, no statement that points and handle are mutually exclusive, and no note on what happens if the contour is open.

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