kicad

Overview Schema Source Related Servers Discussions Admin

save_schematic

Saves the current schematic to disk, optionally to a new file path, and returns success status. Use to persist changes or save a copy.

Instructions

Save the current schematic to disk.

Args: file_path: Optional path to save to. If not provided, saves to original location.

Returns: Dictionary with success status

Examples: >>> # Save to original location >>> result = await save_schematic()

>>> # Save to new location
>>> result = await save_schematic("/path/to/new_location.kicad_sch")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file_path`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 6, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that saving defaults to the original location and returns a dictionary with success status, but it does not mention overwrite behavior, permissions, error cases, or whether the schematic must already be loaded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and organized into Args, Returns, and Examples. The Returns line is somewhat redundant because an output schema exists, but the examples are useful and the overall text is not bloated.

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 simple one-parameter mutation tool with an output schema, the description covers the main invocation path and default behavior. It could be more complete about overwrite/error behavior, but given the low complexity and existing output schema, it is largely sufficient.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It fully explains the single parameter: file_path is an optional path to save to, and when omitted the tool saves to the original location, which adds meaning beyond the schema's bare anyOf/default=null definition.

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 and resource: 'Save the current schematic to disk.' This clearly distinguishes it from sibling operations like load_schematic, create_schematic, and manage_schematic.

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?

It explains that file_path is optional and that omitting it saves to the original location, with examples for both cases. It does not explicitly name alternatives or when-not-to-use conditions, but the usage context is clear for a save operation.

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