Skip to main content
Glama
puran-water

AutoCAD LT AutoLISP MCP Server

by puran-water

annotation

Add text, dimensions, and leaders to AutoCAD LT drawings using AutoLISP commands for precise documentation and labeling.

Instructions

Annotation: text, dimensions, and leaders.

Operations: create_text — data: {x, y, text, height?, rotation?, layer?} create_dimension_linear — data: {x1, y1, x2, y2, dim_x, dim_y} create_dimension_aligned — data: {x1, y1, x2, y2, offset} create_dimension_angular — data: {cx, cy, x1, y1, x2, y2} create_dimension_radius — data: {cx, cy, radius, angle} create_leader — data: {points: [[x,y],...], text}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
dataNo
include_screenshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations indicate readOnlyHint=false, implying mutations, which aligns with 'create' operations in the description. The description adds value by detailing specific operation types and their data structures, but doesn't disclose behavioral traits like permissions, side effects, or rate limits beyond what annotations provide.

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?

The description is appropriately sized and front-loaded with a clear purpose statement. The bulleted list of operations is efficient, though some details could be more structured. No wasted sentences, but minor improvements in clarity are possible.

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?

Given 3 parameters with 0% schema coverage and an output schema exists, the description partially compensates by detailing operations. However, it doesn't fully explain parameter semantics or behavioral context, leaving gaps for a mutation tool with multiple operations.

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 partially does by listing operations and their data fields, but doesn't explain the 'operation' parameter's allowed values or the purpose of 'include_screenshot'. The data structures are described but lack context on units or constraints.

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 clearly states the tool handles annotation operations (text, dimensions, leaders) in AutoCAD, specifying the resource. It distinguishes from siblings like 'drawing' or 'entity' by focusing on annotation creation. However, it doesn't explicitly contrast with all siblings, missing a direct comparison.

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 guidance on when to use this tool versus alternatives like 'entity' or 'drawing' is provided. The list of operations implies usage for creating specific annotation types, but lacks explicit context, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/puran-water/autocad-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server