Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

set_page_size

Set the schematic page size to standard formats or custom dimensions, with optional portrait orientation.

Instructions

Set the schematic page/sheet size.

Args:
    size: Standard name (A5, A4, A3, A2, A1, A0, A, B, C, D, E) or 'User' for custom
    width: Custom width in mm (required when size='User')
    height: Custom height in mm (required when size='User')
    portrait: If True, swap width/height for portrait orientation
    schematic_path: Path to .kicad_sch file. Optional; omit to use the configured default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeYes
widthNo
heightNo
portraitNo
schematic_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations provide no safety profile (all flags false), so the description carries the full burden. It explains parameter effects (portrait swap, custom size) and the optional schematic_path default, but does not disclose that the tool modifies the schematic file, what happens if the file doesn't exist, or whether the change is persistent. This leaves key behavioral aspects undisclosed.

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 purpose sentence followed by a structured Args list. Each line adds necessary information without redundancy, making it easy to scan and parse.

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?

With five parameters, conditional requirements, and an output schema present, the description covers parameter semantics well. However, it omits broader context such as file modification behavior, error conditions, and relationship to other schematic operations. It is adequate for calling the tool correctly but not fully complete for a mutation tool.

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 schema has no parameter descriptions (0% coverage), so the description fully compensates. It lists valid size values, specifies units (mm), marks width/height as conditionally required, explains portrait behavior, and clarifies the optional schematic_path. This is far richer than the bare schema.

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 "Set the schematic page/sheet size" with a specific verb and resource, making the tool's purpose unambiguous. It clearly distinguishes from sibling tools like set_trace_width and set_net_class.

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 provides detailed parameter-level usage instructions (e.g., width/height required when size='User', portrait swaps dimensions), but it does not explicitly state when to use this tool versus alternatives or mention prerequisites like file existence. Usage is implied by the name and description, but not explicitly contextualized.

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