Skip to main content
Glama

chamfer_import_dxf

Imports planar millimeter ASCII DXF text into the active workspace so you can load 2D CAD geometry for editing, analysis, and manufacturing checks.

Instructions

Import planar millimeter ASCII DXF text into the active workspace.

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": {
      "dxf": "<dxf>"
    },
    "name": "chamfer_import_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxfYesASCII DXF content in millimeter units.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description must carry full behavioral disclosure. It states that content goes into the active workspace, but does not explain whether import appends or replaces, how errors are reported, whether existing geometry is affected, or what the tool returns.

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?

One front-loaded sentence with no filler; every term (planar, millimeter, ASCII, active workspace) constrains the operation.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter import operation, the description covers purpose, input format and destination. However, with no annotations or output schema, it leaves behavioral details (merge/replace, errors, return) to inference.

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 exists and schema coverage is 100%, so the schema already defines the dxf string as ASCII DXF in millimeters. The description adds the 'planar' qualifier but little additional syntax or formatting guidance.

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 ('Import') and resource ('DXF text') along with format ('planar millimeter ASCII') and destination ('active workspace'). This is specific enough for an agent to distinguish it from export, execute, get, lint and modify siblings.

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

Usage Guidelines2/5

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

The description supplies applicable input constraints but does not say when to choose this over alternatives such as export or lint, nor when not to use it (e.g., binary or non-millimeter DXF). Usage is only implied by the verb.

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