Skip to main content
Glama

chamfer_lint

Run deterministic 2D geometry and CNC manufacturing checks to detect open contour gaps, self-intersections, duplicate cuts, hole-edge collisions, thin webs, and stray holes before production.

Instructions

Run deterministic 2D geometry and CNC/manufacturing checks (open contour gaps, self-intersections, duplicate cuts, hole-edge collisions, thin webs, stray holes).

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

Input Schema

NameRequiredDescriptionDefault
max_gap_mmNo
manufacturingNo
min_segment_mmNo
min_clearance_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose substantial behavioral content by naming the deterministic checks performed, but it never says whether the tool mutates the drawing, whether findings are returned as a pass/fail report, or what the return format looks like.

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 dense sentence, front-loaded with the verb and purpose, followed by a parenthetical enumeration. There is no filler, and every clause identifies a distinct check class.

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

Completeness2/5

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

With no annotations, no output schema, and four undocumented parameters, the definition is significantly incomplete for a tool that takes numeric tolerances and a manufacturing mode flag. It says what is checked but nothing about tuning those checks or about what the caller receives back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for four parameters, so the description must compensate and does not: max_gap_mm, min_segment_mm, min_clearance_mm, and the manufacturing boolean are never mentioned or mapped to the checks they control. The check names faintly hint at the nature of the thresholds, but no parameter meaning is actually stated.

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 names a specific verb ('Run') and resource ('deterministic 2D geometry and CNC/manufacturing checks') and then enumerates the exact check classes (open contour gaps, self-intersections, duplicate cuts, hole-edge collisions, thin webs, stray holes), so it is unambiguous that this is a validation tool rather than an editor or exporter. It does not explicitly contrast itself with siblings like chamfer_cam_report, but the enumerated checks make the boundary inferable.

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?

No explicit when-to-use, when-not-to-use, or alternative-tool guidance is given. The word 'checks' and the CNC/manufacturing framing imply this should be run before manufacturing or export, but the agent must infer that rather than read it.

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