Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

modify_hierarchical_sheet

Destructive

Update hierarchical sheet properties such as name, file path, width, and height in a KiCad schematic by specifying the sheet UUID.

Instructions

Modify properties of an existing hierarchical sheet block.

Args:
    sheet_uuid: UUID of the sheet to modify (from list_schematic_sheets)
    schematic_path: Path to parent .kicad_sch
    sheet_name: New display name (empty = keep)
    file_name: New file path (empty = keep)
    width: New width in mm (None = keep)
    height: New height in mm (None = keep)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_uuidYes
schematic_pathNo
sheet_nameNo
file_nameNo
widthNo
heightNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate destructiveHint=true. The description adds detail about which properties can be modified and that empty/None keep existing values, but does not disclose additional behavioral traits like permissions or rollback.

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, front-loaded with the purpose, and uses a clear list format for parameters. 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?

For a modification tool with an output schema, the description adequately covers input parameters and their effects. It lacks details about success/failure outcomes but remains complete enough for typical use.

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 fully compensates by explaining each parameter's meaning and behavior (e.g., 'New display name (empty = keep)'). It also specifies the source for sheet_uuid.

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 tool modifies properties of an existing hierarchical sheet block, with a specific verb and resource. It distinguishes from siblings like 'add_hierarchical_sheet' (create) and 'remove_hierarchical_sheet' (delete).

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 indicates the tool is for modifying existing hierarchical sheets and provides a prerequisite (sheet_uuid from list_schematic_sheets). However, it does not explicitly state when not to use it or mention alternatives.

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