Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

remove_hierarchical_sheet

Destructive

Remove a hierarchical sheet block from a KiCad schematic by name or UUID, with optional deletion of the child schematic file.

Instructions

Remove a hierarchical sheet block from a parent schematic.

Identify the sheet by name, uuid, or both. If name matches multiple sheets,
returns an error with UUIDs for disambiguation.

Args:
    parent_schematic_path: Path to parent .kicad_sch
    name: Sheet name to match
    uuid: Sheet UUID for unambiguous identification
    delete_child_file: If True, delete the child .kicad_sch file
          (unless still referenced by another sheet)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_schematic_pathYes
nameNo
uuidNo
delete_child_fileNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses destructive nature (delete_child_file behavior) and error handling, adding context beyond annotations. It explains conditions for file deletion and outputs UUIDs on ambiguity, providing full behavioral transparency.

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 concise with two clear paragraphs. The overview front-loads the purpose, and the Args section is structured. Every sentence adds value without redundancy.

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

Completeness4/5

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

The description covers purpose, identification, error handling, and file deletion. It does not explicitly state what happens if the sheet does not exist, but the output schema covers return values. Minor gap but overall adequate.

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?

With 0% schema description coverage, the description's Args block fully explains each parameter's purpose and behavior. It adds meaning beyond the schema, especially for 'delete_child_file' with its conditional deletion note.

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 it removes a hierarchical sheet block from a parent schematic, with a specific verb and resource. It distinguishes itself from siblings like 'add_hierarchical_sheet' and 'modify_hierarchical_sheet' by the action type.

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 identification methods (name, uuid) and disambiguation behavior when multiple sheets match. It does not explicitly state when not to use or suggest alternatives, but the context is clear enough for an agent to decide.

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