Skip to main content
Glama
ProductOfAmerica

mcp-server-kicad

set_component_property

Set or create any property on a placed component in a KiCad schematic, such as MPN or Tolerance.

Instructions

Set any property on a placed component. Creates it if missing.

Args:
    reference: Component reference (e.g. "R1")
    key: Property name (e.g. "MPN", "Tolerance", "Value")
    value: Property value
    schematic_path: Path to .kicad_sch file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYes
keyYes
valueYes
schematic_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations indicate it's a write operation, and the description confirms setting properties. However, it lacks disclosure of side effects, permissions needed, or reversibility. Minimal additional behavioral context beyond annotations.

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: one line for the main action followed by a compact args list. No wasted words.

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?

Covers purpose and parameter hints but omits return value (output schema exists) and error cases. Adequate but not fully comprehensive given 4 parameters and no schema descriptions.

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

Parameters3/5

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

Schema coverage is 0%, so the description compensates by listing parameters with examples (e.g., 'R1' for reference, 'MPN' for key). However, it does not specify value formats or constraints beyond basic naming.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sets any property on a placed component and creates it if missing. It uses a specific verb and resource but does not differentiate from siblings like 'set_net_class' which targets different resources.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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