Skip to main content
Glama
agtmwebtoon

autocad-mcp

by agtmwebtoon

pid

Create piping and instrumentation diagrams in AutoCAD using a CTO symbol library. Insert symbols, draw process lines, add valves, instruments, pumps, tanks, and flow arrows with predefined layers.

Instructions

P&ID drawing with CTO symbol library.

Operations: setup_layers — Create standard P&ID layers. insert_symbol — data: {category, symbol, x, y, scale?, rotation?} list_symbols — data: {category} draw_process_line — data: {x1, y1, x2, y2} connect_equipment — data: {x1, y1, x2, y2} add_flow_arrow — data: {x, y, rotation?} add_equipment_tag — data: {x, y, tag, description?} add_line_number — data: {x, y, line_num, spec} insert_valve — data: {x, y, valve_type, rotation?, attributes?} insert_instrument — data: {x, y, instrument_type, rotation?, tag_id?, range_value?} insert_pump — data: {x, y, pump_type, rotation?, attributes?} insert_tank — data: {x, y, tank_type, scale?, attributes?}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
operationYes
include_screenshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Beyond the readOnlyHint=false annotation, the description does not disclose behavioral traits such as side effects, permissions, or return values. The operations imply actions (insert, draw, add) but do not detail what changes occur to the drawing or what the output looks like.

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 organized as a list of operations with inline data schemas. It is somewhat long due to the number of operations, but each line is necessary and the format is scannable. The opening sentence is concise and front-loaded with the tool's purpose.

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?

For a tool with many operations, the description does well to enumerate them all, but it lacks semantic details about each operation's behavior and parameters. It also omits the 'include_screenshot' parameter entirely. The output schema likely covers return values, but the description itself is incomplete for a tool of this complexity.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by listing every operation and its corresponding data fields. For instance, 'insert_symbol — data: {category, symbol, x, y, scale?, rotation?}' provides concrete structure for the 'data' parameter, which the schema leaves as an opaque object. This is highly informative.

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

Purpose5/5

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

The description opens with 'P&ID drawing with CTO symbol library', clearly identifying the tool's domain and purpose. The extensive list of operations (insert_symbol, draw_process_line, etc.) specifies exactly what the tool can do, distinguishing it from generic sibling tools like 'drawing' or 'entity'.

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?

The description provides no guidance on when to use this tool versus alternatives. It lists operations but does not state prerequisites, context, or exclusions. For example, it does not clarify when to use this P&ID tool over the generic 'drawing' sibling.

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/agtmwebtoon/autocad-validation-mcp'

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