Skip to main content
Glama

check_circuit

Read-only

Runs electrical, placement, copper and pour design-rule checks on a circuit file, returning error and warning counts plus findings to fix before reporting success.

Instructions

Check the circuit: electrical, placement, copper and pour rules. Answers with the error and warning counts, then up to 20 findings. Run it after autoplace, after autoroute and after removing copper; fix the errors before reporting success.

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": "check_circuit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
filterNo"errors", "warnings", "copper", a part, net, rule or instance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/destructive=false, and the description adds information beyond them: the return contents (counts plus findings) and the significant cap of up to 20 findings, which tells an agent output may be truncated. It does not explain whether the cap is per-severity or how to retrieve the rest, which keeps it below a 5.

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, both load-bearing: the first defines scope and output, the second defines workflow. No filler, and the core purpose is front-loaded before the usage guidance.

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?

With no output schema, the description appropriately explains what comes back (counts plus up to 20 findings), and it covers the workflow around a two-parameter read tool. The one gap is what to do when the 20-finding limit is hit, e.g. whether re-querying with filter is the intended way to see more.

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 100% and both parameters are documented inline, so the schema carries the load. The description's mention of electrical, placement, copper and pour rules loosely explains the kinds of filters available but adds no syntax or format detail beyond the schema.

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 ("Check the circuit") and enumerates the rule domains covered: electrical, placement, copper and pour. It also describes the response shape (error/warning counts plus up to 20 findings). It does not explicitly contrast itself with the summary-style siblings, but the checking semantics are unmistakable.

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 concrete timing guidance tied to named siblings: run after autoplace, after autoroute, and after removing copper, then fix errors before reporting success. It is clear when to use it; it stops short of stating when it is unnecessary or which tool to use instead for pure inspection.

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