cadkit

Overview Schema Source Related Servers Discussions Admin

cad_chamfer

Creates equal-distance chamfers on specified edges using deterministic edge IDs from cad_find_edges, with distance in inches or variable expression.

Instructions

Equal-distance chamfer on edges (deterministic ids from cad_find_edges). distance is inches (number) or an expression/#variable.

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": {
      "documentId": "<documentId>",
      "workspaceId": "<workspaceId>",
      "elementId": "<elementId>",
      "edgeIds": "<edgeIds>",
      "distance": "<distance>"
    },
    "name": "cad_chamfer"
  }
}

Input Schema

Name	Required	Description	Default
`documentId`	Yes
`workspaceId`	Yes
`elementId`	Yes
`edgeIds`	Yes
`distance`	Yes
`name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jun 24, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It mentions equal-distance behavior and deterministic IDs but fails to disclose destructive nature, required permissions, error conditions, or impact on the document.

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 concise sentences with no extraneous text. Front-loaded with core purpose and key usage detail (edge IDs, distance format).

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?

Covers basic purpose and critical parameter semantics, but lacking output description, behavior on failure, prerequisite element state, and details for optional parameters. Adequate for a simple tool but incomplete.

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?

Description explains distance parameter (inches, expression/variable) and source of edgeIds, but does not clarify documentId, workspaceId, elementId, or name. With 0% schema coverage, this is partial but helpful.

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?

Description clearly identifies it as an equal-distance chamfer on edges, and mentions deterministic edge IDs from cad_find_edges. However, it does not explicitly differentiate from similar tools like cad_fillet, leaving potential ambiguity.

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?

Implies usage via cad_find_edges for edge IDs and notes distance units, but lacks explicit guidance on when to use this tool versus alternatives like cad_fillet, and no when-not-to-use instructions.

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