Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

draw_spline

Creates a spline through specified coordinate points, optionally closing the curve, to add curved geometry to an AutoCAD drawing.

Instructions

Сплайн через точки [[x,y],...]. closed: замкнуть.

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": {
      "points": "<points>"
    },
    "name": "draw_spline"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo0
closedNo
pointsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/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 largely drops it: it does not say that this is a mutating drawing operation, which layer/space the entity lands in, whether the spline is created as a new entity, or what happens with fewer than two points. The only behavioral detail disclosed is that 'closed' closes the curve.

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?

Two short fragments with no filler, but the second ('closed: замкнуть') merely restates the parameter name in another language rather than adding meaning, and the whole thing is under-specified rather than genuinely concise.

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?

An output schema exists, so return values need not be described, but for a mutation tool with zero annotations and zero schema coverage the definition is far too thin. Layer targeting and basic validation behavior are left entirely undocumented.

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

Parameters3/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 for three parameters. It does explain the points structure ([[x,y],...]) and glosses 'closed' as 'замкнуть', but leaves 'layer' completely unexplained and gives no constraints (minimum point count, coordinate units).

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+resource: creates a spline through the given points, with the point-list format shown inline as [[x,y],...]. It is distinguishable from siblings like draw_arc or draw_polyline by naming 'spline', though it never 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 Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative guidance is given. The agent must infer on its own whether a spline or draw_polyline is appropriate for a given point sequence.

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