KiCad MCP Pro

Overview Schema Source Related Servers Discussions Admin

mfg_import_allegro

Import Allegro .brd files into a KiCad project directory for conversion to KiCad format. Provide the board file path and optional output directory.

Instructions

Import an Allegro board 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": {
      "allegro_brd_path": "<allegro_brd_path>"
    },
    "name": "mfg_import_allegro"
  }
}

Input Schema

Name	Required	Description	Default
`output_dir`	No
`allegro_brd_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.2Aug 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The annotations only provide openWorldHint, which does little to characterize behavior. The description lacks any disclosure about potential overwrites, required project state, format conversion limitations, or error conditions. It reads as a bare statement of intent with no side effects or edge cases noted.

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, front-loaded sentence with zero wasted words. It is appropriately concise for a straightforward import operation, though brevity comes at the cost of detail evaluated elsewhere.

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?

Despite having an output schema, the description is minimal and fails to convey prerequisites, default behavior for output_dir, or any nuances of Allegro import. For a tool with two parameters and no schema descriptions, this is insufficient to guide an agent on correct invocation.

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 does not compensate by explaining the parameters. It does not mention 'output_dir' or 'allegro_brd_path' at all, leaving their semantics entirely to the schema titles and names.

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 states a specific verb ('Import') and resource ('Allegro board') with a clear destination ('KiCad project directory'). This unambiguously distinguishes it from sibling import tools like mfg_import_geda and mfg_import_pads.

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 when to use the tool (when importing an Allegro board) but gives no explicit context, prerequisites, or exclusions. It does not mention alternatives or when not to use it, such as checking support via mfg_check_import_support first.

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

Deploy Server