Skip to main content
Glama

get_pcb_statistics

Extract PCB size, layer count, component counts, and design rules from a .kicad_pcb file to inspect board statistics.

Instructions

Give the size, the layers, the counts and the design rules of a board.

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_path": "<file_path>"
    },
    "name": "get_pcb_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesThe .kicad_pcb file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about read-only behavior, parsing cost, error handling for a malformed or missing .kicad_pcb file, or whether 'design rules' means declared rules versus violations. It mainly restates the categories of returned data rather than disclosing behavioral traits.

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?

One short sentence, front-loaded with the resource and the reported fields, with no filler or repetition.

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?

An output schema exists, so return values need not be explained, and the sole parameter is fully documented in the schema. However, for a board-inspection tool in a crowded analysis family, the description lacks routing guidance against siblings and any note on failure modes, leaving meaningful gaps.

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 parameter with 100% schema description coverage ('The .kicad_pcb file.'), so the schema already defines it and the baseline is 3. The description adds no path format, relative-vs-absolute guidance, or file-extension constraints beyond what the schema states.

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?

Names a concrete resource (a board / .kicad_pcb file) and enumerates the specific outputs: size, layers, counts, design rules. That is enough to distinguish it from deeper analysis siblings such as analyze_pcb_nets or get_drc_violations, though the verb 'Give' is weak and no sibling is named explicitly.

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?

No statement of when to use this versus analyze_pcb_nets, analyze_pcb_power_integrity, or get_drc_violations, and no prerequisites or exclusions. Usage is only inferable from the enumerated outputs.

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