Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

document_save

Saves the active AutoCAD drawing to its existing file path, persisting unsaved changes; when a path is supplied, writes the drawing to that destination instead.

Instructions

Save the currently bound document to its verified existing path, or delegate to SaveAs when path is supplied; success requires immediate persisted-clean readback.

Side-effects: Persists unsaved drawing changes to disk and clears dirty state. Disambiguation: Use document_save to persist changes in-place; use document_save_as to write to a new destination path.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOptional file destination path; if omitted saves in-place to currently bound path

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: +"Optional file destination path; if omitted saves in-place to currently bound path"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, so the description carries real weight and it delivers: it discloses the side-effect (unsaved drawing changes persisted to disk, dirty state cleared), the precondition (path must be a verified existing path), and a success criterion (persisted-clean readback). It stops short of saying what happens on failure (e.g. whether dirty state remains or an error is raised when the bound path is stale), which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact lines, each with a distinct job: core behavior front-loaded, then side-effects, then disambiguation. No filler or repetition of structured fields.

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 mutation tool with only a readOnlyHint annotation, the definition covers purpose, precondition, side-effect, success criterion, and sibling routing. An output schema exists, so return values need not be described, and nothing an agent needs to invoke this correctly is missing.

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 coverage is 100% and the single parameter is well documented, so the baseline is 3. The description adds beyond the schema by explaining that supplying path re-routes behavior to SaveAs and that omission saves in-place against the currently bound path, which is a behavioral consequence rather than a restatement of the schema text.

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 ('Save the currently bound document') plus the exact scope: in-place save to a verified existing path, with delegation to SaveAs when a path is given. The sibling document_save_as is named and differentiated, so an agent can pick between them without opening either 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 gives an explicit routing rule: use document_save to persist in-place, use document_save_as to write to a new destination. The optional path parameter's effect ('delegate to SaveAs when path is supplied') reinforces the same rule from the parameter side.

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