Skip to main content
Glama

add_hole

Add a non-plated mounting hole to a circuit file in one change by specifying X/Y coordinates and diameter.

Instructions

Add a non-plated mounting hole as ONE change.

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": {
      "file": "<file>",
      "x": "<x>",
      "y": "<y>",
      "diameter": "<diameter>"
    },
    "name": "add_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileYesCircuit file
diameterYesmm

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'As ONE change' hints that the operation is atomic (a single undo unit), which is genuinely useful, but nothing is said about required file state, permissions, whether the file is modified in place, or what is returned.

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?

Eight words, front-loaded with the verb and resource, with no padding. The emphasized 'ONE change' is slightly cryptic but does not waste space.

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?

A mutation tool with no annotations, no output schema, and half its parameters undocumented needs considerably more: units and coordinate frame for x/y, and what the resulting change looks like. As written, an agent could call it but could easily place the hole incorrectly.

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 coverage is 50%: only file ('Circuit file') and diameter ('mm') are documented, while x and y have no description anywhere. The description adds no coordinate convention, origin, or unit information to compensate for that gap.

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?

Names a concrete verb and resource ('Add a non-plated mounting hole'), which is specific enough to separate it from remove_hole and the add_* siblings. It stops short of differentiating itself explicitly from alternatives, but the operation is unmistakable.

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?

No when-to-use, when-not-to-use, or prerequisite information is given. An agent is left to infer that this is for non-plated mechanical holes rather than vias or pads, and no guidance connects it to remove_hole or add_via.

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