Skip to main content
Glama

remove_hole

Destructive

Delete a non-plated hole by ID from a circuit file as one change, refusing locked holes and resolving instance holes in their sheet file.

Instructions

Remove a non-plated hole by id as ONE change. Locked holes are refused; a hole inside an instance ("PS1/hole:1") lives in its sheet file.

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>",
      "id": "<id>"
    },
    "name": "remove_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYese.g. "hole:1"
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true; the description adds real behavior beyond that: an atomicity/undo unit ('as ONE change'), a documented refusal case for locked holes, and the addressing rule for holes nested in instances. It omits what the response returns on success, which is the only notable gap.

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 sentences, no filler, and the core action and its atomicity are front-loaded before the edge-case rules. Every clause carries distinct information (atomicity, refusal, nested addressing).

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?

For a two-parameter destructive tool with no output schema, the description covers the action, the failure case, and the tricky addressing scenario. Only the return/confirmation behavior is unstated, a minor gap for such a narrow operation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point by extending the id format beyond the schema's bare 'hole:1' example to the instance-qualified path form 'PS1/hole:1'. The 'file' parameter is left to the schema's 'Circuit file' description.

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?

Specific verb ('Remove') plus resource ('non-plated hole') and selector ('by id'), with a scoping qualifier that separates it from copper/part/pour removals in the sibling list. It stops short of naming any sibling explicitly, so an agent must infer the boundary from the 'non-plated hole' qualifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete preconditions: locked holes are refused, and a hole inside an instance must be addressed through its sheet file ('PS1/hole:1'). It does not name an alternative tool, but the exclusion conditions are clear enough to prevent most mis-calls.

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