Skip to main content
Glama

board_summary

Read-only

Summarize a circuit board file into a compact or full report covering size, layers, part placement, longest connections, overlaps, pours, silkscreen, drawings, and unrouted counts.

Instructions

The board in about 60 lines: size, layers, courtyard use, one line per part (position, side, [LOCKED] or "not placed"), the ten longest connections, overlaps, parts off the board, pours, silkscreen texts, drawings, unrouted count.

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

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
detailNo"compact" (default, about 60 lines) or "full"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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 real value beyond that by disclosing the report's structure, approximate size (~60 lines), and the marker conventions ([LOCKED], "not placed") an agent will see in the output. It says nothing about cost or latency, but for a read-only report that is a minor omission.

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 sentence, front-loaded with the payload size, then a colon-delimited inventory — dense with no filler. The list is long but each item earns its place by telling the agent what sections to expect.

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 only two parameters, a 100% covered schema, and no output schema, the description's main burden is describing what comes back — and the content inventory does that thoroughly, including edge-case markers for locked and unplaced parts. The unexplained 'full' mode is the only real gap.

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 description coverage is 100%, so the schema already documents both `file` and the `detail` enum, which sets the baseline at 3. The description reinforces the compact default with 'about 60 lines' but never explains what 'full' returns, leaving the one non-trivial parameter choice to the schema alone.

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?

The description names the resource (the board) and enumerates exactly what the summary contains: size, layers, courtyard use, per-part lines with position/side/LOCKED/not-placed markers, longest connections, overlaps, off-board parts, pours, silkscreen texts, drawings, unrouted count. That content inventory distinguishes it from circuit_summary and copper_summary by scope, even though no sibling is named. It falls short of a 5 only because the verb is implicit ('The board in about 60 lines') rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement, and no alternative is named. The enumerated contents imply this is a first-look overview tool, but the agent must infer that on its own, and nothing tells it whether circuit_summary or copper_summary is the better starting point.

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