Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

partdesign_hole

Drill parametric simple, counterbore, countersink, or threaded holes from a Sketch, with undo support for safe FreeCAD modeling.

Instructions

Drill parametric simple, counterbore, countersink, or threaded holes from a Sketch (undoable).

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": {
      "sketch_name": "<sketch_name>"
    },
    "name": "partdesign_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
depthNo
diameterNo
doc_nameNo
reversedNo
threadedNo
sketch_nameYes
through_allNo
hole_cut_typeNoNone
hole_cut_depthNo
hole_cut_diameterNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the safety bar is lower. The description adds genuine value with '(undoable)' and 'parametric', indicating the feature is reversible and lives in the feature tree. It does not explain what happens on re-invocation, what the default hole_cut_type='None' means, or how threading is derived.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that packs the verb, resource, variants, input source, and reversibility with no wasted words. It is terse to the point of under-specification, but structurally sound.

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?

An output schema exists, so return values need not be described, and annotations cover the mutation profile. However, for an 11-parameter parametric CAD feature with zero schema coverage, the one-sentence description leaves too much unspecified for an agent to choose parameter values confidently.

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% across 11 parameters, so the description carries the full burden, yet it only loosely maps to hole_cut_type via the hole-type list. It says nothing about depth vs through_all interaction, reversed, hole_cut_depth/hole_cut_diameter, doc_name, or units, leaving most parameters semantically opaque.

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?

States a specific verb and resource ('Drill ... holes') and enumerates the hole variants (simple, counterbore, countersink, threaded), plus the source ('from a Sketch'). That is enough for an agent to distinguish it from siblings like partdesign_groove or boolean_operation, though no sibling is named explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no statement that a pre-existing Sketch is a hard prerequisite (it is only implied by 'from a Sketch'). Nothing tells the agent how this differs from other material-removal tools in the catalog.

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