Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

flatten_hierarchy

Combine hierarchical schematic sheets into one flat schematic file. Merges all child content with offset positions, preserving the original hierarchy.

Instructions

Flatten a hierarchical schematic into a single sheet.

Merges all child sheet content into one schematic with offset positions.
Creates a new file — does NOT modify the original hierarchy.

Args:
    schematic_path: Path to root .kicad_sch file
    output_path: Path for flattened output (defaults to *_flat.kicad_sch)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schematic_pathNo
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that it 'Creates a new file' and does not modify the original, which is consistent with destructiveHint=false. It adds context to the annotations by explicitly stating the non-destructive behavior and output path behavior.

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 extremely concise: four sentences covering purpose, behavior, and arguments. No superfluous words, and the most important information (purpose) is front-loaded.

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

Completeness5/5

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

Given the tool's simplicity (two parameters, no required params), the description is complete. It explains the transformation, input/output, and safety (no modification). The presence of an output schema likely covers return values, so no additional detail is needed.

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

Parameters5/5

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

The description provides detailed natural language explanations for both parameters (schematic_path and output_path) in the Args section, which is especially valuable given the 0% schema description coverage. It clarifies the input and output paths with defaults.

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 a specific verb and resource: 'Flatten a hierarchical schematic into a single sheet.' It distinguishes itself from siblings like 'list_hierarchy' and 'validate_hierarchy' by focusing on flattening into a single sheet.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool (to flatten a hierarchy) and what it does not do ('does NOT modify the original hierarchy'). However, it does not explicitly state when not to use it or alternatives beyond the sibling context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProductOfAmerica/mcp-server-kicad'

If you have feedback or need assistance with the MCP directory API, please join our Discord server