Skip to main content
Glama

chamfer_export_dxf

Export verified 2D drawings to ASCII R2010 millimeter DXF files, optionally saving to a local .dxf path while preventing accidental overwrites.

Instructions

Export the verified 2D drawing to ASCII R2010 millimeter DXF. Optionally write the output to a local .dxf file path (refuses to overwrite unless overwrite=true).

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

Input Schema

NameRequiredDescriptionDefault
overwriteNoAllow replacing an existing file at output_path.
output_pathNoOptional .dxf file path where the file will be saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose a real safety trait — it refuses to overwrite an existing file unless overwrite=true. However it never says what is returned when output_path is omitted (DXF text? a summary?), nor whether a failed verification blocks export, leaving the main behavioral question unanswered.

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?

Two sentences, zero filler, with the format specification front-loaded and the path/overwrite caveat in the second sentence. Every clause carries information an agent would otherwise have to guess.

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?

For a two-optional-parameter export tool with no output schema, the definition covers format, optional file destination, and overwrite protection, which is nearly everything needed. The one missing piece is the return behavior when no path is given, which matters because the file write is explicitly optional.

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 description coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds genuine meaning beyond the schema by explaining the default consequence of overwrite=false — the export is refused rather than silently failing — and by framing output_path as optional file output rather than a required destination.

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

Purpose4/5

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

States a specific verb (export), resource (the verified 2D drawing) and exact output format (ASCII R2010 millimeter DXF), which is far more informative than the name alone. It does not explicitly contrast with chamfer_import_dxf or other siblings, but the import/export split in the name pairs is self-evident.

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

Usage Guidelines3/5

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

The phrase 'verified 2D drawing' implies a prerequisite that the drawing must be verified (e.g., via chamfer_lint) before export, and 'optionally write... to a local .dxf file path' implies in-memory output when the path is omitted. Neither is stated explicitly and no alternative tool is named, so guidance is implied rather than given.

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