Skip to main content
Glama
Sign In
KiCad MCP Pro

KiCad MCP Pro

by Valxyria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

mfg_import_pads

Import PADS PCB files into a KiCad project directory for further editing and design within KiCad.

Instructions

Import a PADS PCB into a KiCad project directory.

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": {
      "pads_pcb_path": "<pads_pcb_path>"
    },
    "name": "mfg_import_pads"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_dirNo
pads_pcb_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.2

TDQS

B3.4/5.0
Behavior2/5

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

The description lacks any detail about side effects, such as whether existing files are overwritten or if the project is modified in place. Annotations provide only openWorldHint, which doesn't disclose safety or destructive behavior, so the description carries the full burden and falls short.

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?

The description is a single, focused sentence that is immediately understandable and free of unnecessary words. It prioritizes the core purpose effectively.

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?

The description covers the core purpose but omits details about import behavior, such as handling of existing data, optional output_dir behavior, and any required project state. Given the tool's simplicity, it is minimally adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description should explain the parameters, but it only mentions 'PADS PCB' generically. The parameter names pads_pcb_path and output_dir are suggestive but the description does not clarify defaults, requiredness, or expected formats.

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?

The description clearly states the action 'Import', the input 'PADS PCB', and the destination 'KiCad project directory', making it distinct from sibling import tools for Geda and Allegro.

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 description implies usage when a PADS PCB needs to be imported, but it does not explicitly mention alternatives or when not to use it. There is no comparison with mfg_import_geda or mfg_import_allegro.

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