Skip to main content
Glama

cad_file

Destructive

Perform file-level operations on CAD documents: create, open, save, close, delete, list, import, and export interop files like STEP, DXF, STL, DWG, or JSON.

Instructions

Create, open, save, close, delete, list, import or export files.

聚合文件操作。按 ``action`` 派发:create / open / save / close / delete /
list / import / export。
- ``create`` / ``open`` / ``save`` / ``close`` / ``delete`` / ``list``:
  manage in-memory documents. ``open`` and ``save`` read/write the JSON
  scene format; ``create`` starts a new document (optional ``template`` /
  ``unit``).
- ``export``: write the current document to an interop format — step
  (recommended), dxf, stl, dwg or json — at ``path``.
- ``import``: load an interop file (.json / .dxf / .step / .dwg) as a new
  document.

When not to use: ``cad_file`` handles whole files/documents. For
per-object geometry edits use ``cad_object``; to import/export raw JSON
scene data (not files) use ``cad_json`` (import_scene/export_scene).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesFile action to perform, discriminated by `action`: create, open, save, close, delete, list, import or export.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoSaved / exported path
filesNoOpen files
actionYesFile action executed
statusYesOperation status
file_idNoFile unique identifier
messageNoStatus description
filenameNoFile name
object_countNoNumber of imported objects
Behavior4/5

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

Annotations already set destructiveHint=true, and the description aligns by listing 'delete' and 'save' actions. It adds context beyond annotations: open/save use JSON scene format, create accepts template/unit, export/import handle interop formats. No contradiction found.

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?

Description is well-structured and front-loaded: starts with a one-line summary, then action details, then exclusions. Every sentence adds value; no redundancy or fluff.

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?

The description covers all 8 actions, dispatch model, file formats, and sibling differentiation. Since an output schema exists, return-value details are not required. The description is complete for a complex multi-action tool.

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 covers 100% of parameters, so baseline is 3. The description adds meaningful semantics by summarizing action behavior (e.g., export writes to interop formats, import loads .json/.dxf/.step/.dwg), which complements the schema. It mentions .dwg import not explicitly in the schema's import path description.

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 clearly states the tool's scope: 'Create, open, save, close, delete, list, import or export files.' It uses a specific verb list and explicitly differentiates from siblings by saying 'For per-object geometry edits use cad_object; to import/export raw JSON scene data (not files) use cad_json'.

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 description includes a 'When not to use' section that names concrete alternative tools (cad_object, cad_json), and gives format guidance (e.g., 'step (recommended)'). This is explicit guidance on when to use and when to avoid.

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/Tianshang301/TianshangCAD'

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