Skip to main content
Glama

chamfer_cam_report

Computes laser/CNC manufacturing telemetry for the active 2D drawing: total cutting path length, pierce count, net part area, scrap percentage, and sheet mass from a given thickness.

Instructions

Compute laser/CNC manufacturing telemetry for the active 2D drawing: total cutting path length (mm), pierce count, net part area (mm2), scrap percentage, and sheet mass.

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

Input Schema

NameRequiredDescriptionDefault
thickness_mmNo

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?

No annotations are supplied, so the description carries the full behavioral burden; 'compute' implies a non-mutating calculation, and 'for the active 2D drawing' discloses the precondition that a drawing must be active. However, it does not say what happens when no drawing is active, whether the call has side effects on the drawing state, or whether results are cached or recalculated.

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 with the action front-loaded and the output list appended; every clause names a distinct metric or unit and nothing is repeated.

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?

With no output schema, the description correctly takes on the job of enumerating returned metrics and their units, which is the main missing piece. Remaining gaps are modest for a one-parameter read tool: no explanation of thickness_mm's effect on mass and no error/empty-drawing behavior.

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?

The single parameter thickness_mm is completely absent from the description, and the schema only gives type number, default 3 and exclusiveMinimum 0 with 0% description coverage. The agent must guess that thickness feeds the sheet-mass calculation and has no stated units beyond what the name implies, so the description does not compensate for the coverage gap.

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 (compute) and resource (laser/CNC manufacturing telemetry for the active 2D drawing) and enumerates exactly which metrics are produced: path length, pierce count, part area, scrap percentage, sheet mass. This clearly separates it from the mutation/IO siblings like chamfer_execute, chamfer_export_dxf and chamfer_modify_entity.

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: an agent can infer this is the analysis step that follows loading/importing a drawing and precedes executing or exporting. The description never says when to call it versus chamfer_lint or chamfer_get_drawing, offers no prerequisites or exclusions, and no explicit 'when not to use'.

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