Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

document_open

Load an existing DWG or DXF file by path and make it the active document for editing or inspection.

Instructions

Open an existing allowed DWG/DXF path as the active document; changes session state.

Side-effects: Changes active document session. Disambiguation: Use to load an existing drawing; use document_new to create a blank drawing.

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": {
      "path": "<path>"
    },
    "name": "document_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFilesystem path to the existing DWG or DXF file to open

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / path / description
      Added value: +"Filesystem path to the existing DWG or DXF file to open"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description adds a side-effects line and a disambiguation line beyond the readOnlyHint=false annotation, making clear this mutates session state rather than the file system. It does not cover failure modes (nonexistent path, blocked file, what 'allowed' means), which is a gap for a state-changing tool but not a contradiction.

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?

Front-loaded main clause followed by compact side-effect and disambiguation lines; every line is labeled and scannable. Minor redundancy between 'changes session state' and 'Side-effects: Changes active document session' costs a point.

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

Completeness4/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 no explanation, and the one parameter is fully schema-documented. The only unresolved item is the undefined 'allowed' qualifier, which an agent may not be able to evaluate before calling.

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 100% and the single path parameter is documented as a 'Filesystem path to the existing DWG or DXF file to open'. The description adds only the implicit constraint that the file must already exist and be 'allowed', but does not define that constraint. Baseline 3 applies.

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?

States a specific verb and resource — 'Open an existing allowed DWG/DXF path as the active document' — and scopes it to two file types. An agent knows exactly what the tool does without opening the schema.

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

Usage Guidelines5/5

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

The disambiguation line explicitly contrasts it with document_new ('use document_new to create a blank drawing'), covering both when to use this tool and when to use the sibling instead. Nothing is left to inference.

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

Deploy Server

Other Tools