Skip to main content
Glama

copper_summary

Read-only

Summarizes copper totals, per-net tracks/vias/unrouted counts, pours and holes by ID, and rule violations in up to 60 lines. Run before and after drawing copper to compare changes.

Instructions

Summarize the copper in at most 60 lines: totals, per net (tracks, vias, unrouted), pours and holes by id, violations by rule. Call it before and after drawing copper.

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

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered. The description does add real behavioral context beyond them — the output is capped at 60 lines and broken into named sections — but with no output schema the description leaves the return format and failure behavior (bad or missing circuit file) unspecified.

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. The output-size cap and section list are front-loaded, and the timing instruction follows as a distinct second sentence.

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 read-only reporting tool with annotations covering safety, the description adequately explains what comes back and when to call it. The remaining gap is only how the file argument is identified, which is the one thing an agent could still get wrong.

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?

There is a single required parameter with 100% schema description coverage ("Circuit file"), so the schema carries the load. The description adds nothing about it — not whether it is a path, a filename, or a handle returned by list_circuits — so baseline 3 applies.

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 (summarize) and resource (copper) and then enumerates exactly what the summary contains: totals, per-net tracks/vias/unrouted, pours and holes by id, violations by rule. That enumeration separates it cleanly from the broader board_summary and circuit_summary siblings without needing to name them.

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?

"Call it before and after drawing copper" gives concrete timing guidance tied to the drawing workflow, which points the agent at the right moment relative to add_trace/add_via/add_pour. It stops short of explicit when-not guidance or naming an alternative for non-copper questions.

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