Skip to main content
Glama

chamfer_get_drawing

Read the active millimeter 2D CAD drawing state, including layers, entities and revision, plus its deterministic geometry verification summary for checking accuracy.

Instructions

Read the active millimeter 2D CAD drawing state (layers, entities, revision) and its deterministic geometry verification summary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 must carry the behavioral burden. It does imply a non-mutating read and discloses the shape of what comes back (layers, entities, revision, deterministic verification summary), but says nothing about cost, caching, failure modes, or whether the 'active' drawing can be absent.

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?

A single front-loaded sentence with no filler; the read action comes first and the returned contents follow immediately. Nothing is redundant or padded.

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 zero-parameter read tool with no annotations and no output schema, the description compensates reasonably by enumerating the returned fields, effectively standing in for the missing output schema. It could be stronger only by noting whether the drawing must already exist or be imported first.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. It helpfully clarifies that no drawing identifier is needed because it always targets the 'active' drawing, which is the one piece of semantic context a parameterless tool can offer.

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?

The description uses a specific verb ('Read') and a precisely scoped resource ('the active millimeter 2D CAD drawing state'), then enumerates what that state contains: layers, entities, revision, plus a geometry verification summary. This clearly separates it from mutating siblings like chamfer_modify_entity or chamfer_execute, though it never names an alternative explicitly.

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?

Usage is only implied: the word 'active' signals it operates on the current drawing without any selection parameter, and 'verification summary' hints at a pre-check role. There is no explicit statement of when to call this versus chamfer_lint or chamfer_cam_report, and no preconditions or exclusions are given.

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