kicad-mcp-layer

Overview Schema Source Related Servers Discussions Admin

review_project

Read-onlyIdempotent

Run every schematic and board check for a KiCad project against fab limits, returning one report with a verdict and any checks that could not run.

Instructions

The full review of a project: every schematic check followed by every board check, in one report with one verdict and the list of checks that could not run.

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": {
      "path": "<path>"
    },
    "name": "review_project"
  }
}

Input Schema

Name	Required	Description	Default
`fab`	No	Whose manufacturing limits to check against. jlcpcb picks 2- or 4-layer limits from the board.	jlcpcb
`path`	Yes	A project directory or any file in it.

Output Schema

Name	Required	Description
`fab`	No
`kind`	Yes
`checks`	Yes
`counts`	Yes
`target`	Yes
`verdict`	Yes	Worst verdict of the checks that ran. Unverified checks are listed separately and never hidden.
`duration_s`	Yes
`unverified`	No	Checks that could not run, with their reasons in the check summaries.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context—it is a compound run producing one verdict plus a list of checks that could not run—but does not cover cost, runtime, or failure handling.

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?

A single sentence, front-loaded with the core action and scope, with zero filler. Every clause earns its place.

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 an output schema present and annotations covering the safety profile, the definition needn't explain return values, and it still conveys the compound nature and the verdict+failed-checks output. Only the absence of any selection guidance keeps it from being fully complete.

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 both parameters (path and the fab enum) are already fully documented in the schema. The description adds nothing beyond that, making the baseline 3 appropriate.

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?

Specific verb+resource ('full review of a project') with explicit scope: every schematic check plus every board check in one report. This scope contrast lets an agent distinguish it from the individual review_schematic and review_board siblings without opening any schema.

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?

The compound scope implies 'use this for an all-in-one review rather than the per-layer review tools,' but no sibling is named and there is no explicit when-to-use/when-not guidance. Usage is inferable rather than stated.

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