Skip to main content
Glama

remove_trace

Destructive

Delete a schematic trace between two selectors in either direction to break an unwanted connection in a circuit file. Provide the file and both selector endpoints.

Instructions

Schematic trace (a connection, not copper): remove the one between two selectors (in either direction).

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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "remove_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fileYesCircuit file
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral detail — the two selectors are order-independent ('in either direction') — but says nothing about whether removal updates netlist connectivity, whether it fails if no trace exists, or whether the edit is undoable.

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 tight sentence with the resource and the key disambiguation front-loaded; 'a connection, not copper' earns its place. The 'between two selectors (in either direction)' phrasing is slightly dense but not wasteful.

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?

For a 3-parameter destructive tool with no output schema and low schema description coverage, the definition covers purpose and selector ordering but omits selector syntax, failure modes, and post-removal effects — enough to attempt the call, not enough to call it confidently.

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?

Schema coverage is only 33% (only 'file' is documented), so the description must compensate. It does add meaning for from/to by calling them 'selectors' whose order is irrelevant, but it never explains what a selector string looks like or what the file argument expects, leaving real gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (remove) and resource (schematic trace), and explicitly disambiguates it from copper removal with 'a connection, not copper', which separates it from sibling remove_copper without opening either schema.

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?

The parenthetical 'a connection, not copper' implicitly tells the agent when to pick this over remove_copper, but there is no explicit alternative named, no prerequisite or state guidance, and no statement of what happens to the rest of the schematic.

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