Skip to main content
Glama

remove_pour

Destructive

Deletes a copper pour by ID as one change; locked pours are refused, and instance pours are removed from their sheet file.

Instructions

Remove a copper pour by id as ONE change. Locked pours are refused; a pour inside an instance ("PS1/copperpour: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_pour"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true, so the description carries real weight and delivers: it discloses undo granularity ("as ONE change"), a failure mode (locked pours are refused), and path-resolution behavior for instance-scoped pours. It stops short of saying what is returned or whether the removal is reversible, but the behavioral value added is substantial.

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 short sentences, front-loaded with the action and its identifier, then the two caveats that actually affect calling it. No filler or restatement of the name.

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 key risks: scope granularity, refusal condition, and file/id resolution across sheets. Only the return behavior or confirmation of what the file looks like afterward is left unstated.

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 already 100%, so the baseline is 3, but the description adds non-obvious semantics: the id may be instance-qualified ("PS1/copperpour:1") and in that case the file must be the sheet file rather than the top-level circuit. That goes meaningfully beyond the schema's flat example "copperpour:1".

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 ("Remove a copper pour by id") and distinguishes it from remove_copper/remove_trace by naming the exact object type and key. It does not explicitly name a sibling alternative, so it falls short of a 5, but an agent can tell which tool to pick.

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 implied through constraints rather than stated as routing: locked pours are refused and instance-scoped pours must be addressed in their sheet file. There is no explicit when-to-use-vs-alternative guidance, e.g. add_pour or remove_copper, so the agent must infer the selection rule.

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