Skip to main content
Glama

circuit_summary

Read-only

Summarize a circuit file with one line per part and net, plus locked parts, human marks, and lock violations; filter by sub-sheet or list full properties and traces.

Instructions

Summarize a circuit: one line per part and per net, then locked parts, marks from the human and lock violations. filter "PS1" shows one sub-sheet instance; detail "full" lists every prop and trace.

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

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
detailNoDefault "compact"
filterNoA sub-sheet instance, e.g. "PS1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context by enumerating what the report contains (locked parts, human marks, lock violations), but says nothing about size, cost, or how much output 'full' produces on a large circuit.

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?

Two dense sentences with no filler, and the primary behavior is front-loaded before the parameter notes. The telegraphic phrasing ("marks from the human") is slightly cryptic but recovers in context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 does the necessary work of describing the return shape as a sectioned report, and it covers both optional parameters' effects. Nothing an agent needs in order to call a read-only summary tool correctly is missing.

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 description coverage is 100%, so the baseline is 3, and the description goes beyond it by explaining the concrete effect of each optional parameter: filter scopes to a single sub-sheet instance and detail "full" enumerates every prop and trace. Only the required 'file' parameter is left to the schema, which is appropriate since it is self-evident.

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 ("Summarize a circuit") and even outlines the report structure: one line per part and per net, then locked parts, human marks, and lock violations. It is clearly a read/report tool distinct from mutation siblings like edit_circuit or add_trace, though it never explicitly says how it differs from board_summary or copper_summary beyond the word 'circuit'.

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 rather than prescribed: it explains the effect of the two optional parameters (filter "PS1" narrows to one sub-sheet instance, detail "full" expands every prop and trace), which helps an agent choose values. There is no explicit when-to-use/when-not guidance or named alternative for getting a board-level or copper-level summary instead.

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