Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

document_save_as

Save the active drawing to a new allowed DWG or DXF file, verify the saved path and persisted-clean state, then update document binding; use to fork or save under a new name.

Instructions

Save the active document to an allowed DWG/DXF destination, verify the same bound path and immediate persisted-clean state, then update its document scope.

Side-effects: Writes drawing to new file path, updates document binding. Disambiguation: Use to fork or save drawing under a new name; use document_save for in-place save.

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_save_as"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAllowed destination filesystem path (.dwg or .dxf) for the saved drawing

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: +"Allowed destination filesystem path (.dwg or .dxf) for the saved drawing"
  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?

Annotations only declare readOnlyHint=false, so the description carries the behavioral burden and does so with a Side-effects section: writes to a new file path, verifies the bound path and persisted-clean state, and updates document scope. It stops short of covering error/permission behavior or what happens on an invalid destination, but the core mutation traits are disclosed.

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-loads the save action, then uses labeled Side-effects and Disambiguation sections that each earn their place. Slightly dense phrasing ('verify the same bound path and immediate persisted-clean state') but no filler sentences.

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-value explanation is unnecessary, and the description covers the mutation, side-effects, and sibling distinction. What remains missing is failure-mode behavior for a disallowed path, a minor gap for a write tool with minimal annotations.

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?

Only one parameter, and the schema already documents it at 100% coverage, including the .dwg/.dxf constraint. The description reinforces 'allowed DWG/DXF destination' but adds no syntax or validation nuance beyond the schema, so baseline 3 is appropriate.

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 (save) plus resource (active document) with the 'as' semantics (new DWG/DXF destination) clearly conveyed. It explicitly differentiates itself from document_save, so an agent can route 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 names both when to use this tool ('fork or save under a new name') and the alternative ('document_save for in-place save'). Usage conditions and exclusions are explicit.

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