Skip to main content
Glama
Sign In
KiCad MCP Pro

KiCad MCP Pro

by Valxyria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

manufacturing_quality_gate

Read-onlyIdempotent

Evaluate PCB manufacturing readiness by checking against DFM profiles, flagging design issues before fabrication.

Instructions

Evaluate manufacturing readiness against the active or requested DFM profile.

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

Input Schema

NameRequiredDescriptionDefault
tierNo
manufacturerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that evaluation is based on an 'active or requested DFM profile,' which is useful state context, but does not disclose output behavior or profile-loading requirements.

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, front-loaded sentence conveys the core purpose with no filler. It is appropriately concise, though the brevity contributes to missing details.

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?

With an output schema present and readOnly/idempotent annotations, the description need not explain return values or safety. However, it lacks context about the DFM profile lifecycle, how to request a profile via tier/manufacturer, and how it differs from sibling DFM/quality-gate tools, leaving it minimally complete.

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

Parameters2/5

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

Input schema covers 0% of parameters with descriptions. The description never mentions 'tier' or 'manufacturer' or how they influence the requested DFM profile, so the agent gets no semantic guidance beyond their names.

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 states a specific action ('Evaluate manufacturing readiness') against a clear resource ('active or requested DFM profile'). It is clear and distinct from the generic quality-gate sibling names, though it does not explicitly differentiate from dfm_run_manufacturer_check or check_design_for_manufacture.

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?

It implies the tool is for readiness evaluation tied to a DFM profile but gives no explicit when-to-use or when-not-to-use guidance. There is no mention of alternatives or prerequisites, so the agent must infer usage from context.

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