Skip to main content
Glama
Sign In
KiCad MCP Pro

KiCad MCP Pro

by Valxyria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

project_quality_gate_report

Generate a structured project quality gate report to identify design issues and assess manufacturing readiness.

Instructions

Return the full project gate in structured form for capable MCP clients.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_quality_gate_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNo
manufacturerNo

Output Schema

NameRequiredDescriptionDefault
textYes
statusYes
summaryYes
outcomesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.2

TDQS

C2.4/5.0
Behavior2/5

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

Annotations are empty, so the description must carry behavioral disclosure. It only states the return action; it does not mention whether the tool runs checks, is read-only, requires prior setup, or how the 'gate' is computed. 'Structured form' hints at output shape but not behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence and front-loaded, but the phrase 'for capable MCP clients' adds no value and is unhelpful fluff. It is concise but not effectively informative.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, but the description still does not explain what constitutes the 'full project gate', how parameters influence the result, or how this relates to project_quality_gate. Given a project with many quality-gate siblings, the tool is under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description omits any mention of the 'tier' and 'manufacturer' parameters, leaving their purpose and allowed values entirely unclear. With two optional parameters, the description must compensate, and it does not.

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 uses the specific verb 'Return' and identifies the resource as 'the full project gate in structured form', which distinguishes this report tool from sibling like project_quality_gate. However, 'project gate' is unexplained jargon, so clarity is good but not excellent.

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 guidance about when to use this tool versus alternatives such as project_quality_gate or pcb_placement_quality_report. The 'for capable MCP clients' phrase is not a usage guideline.

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

Deploy Server

Other Tools