kicad

by 5nail000

Overview Schema Source Related Servers Discussions Admin

Python

Local

add_wire

Create a wire between two points to connect component pins and form electrical nets in a schematic.

Instructions

Add a wire between two points.

Creates a wire connection between start and end points. Wires are used to connect component pins and establish electrical nets.

Args: start: Start point as (x, y) tuple in mm end: End point as (x, y) tuple in mm ctx: MCP context for progress reporting (optional)

Returns: Dictionary with success status and wire information

Examples: >>> # Connect two points horizontally >>> result = await add_wire( ... start=(100.0, 100.0), ... end=(150.0, 100.0) ... )

>>> # Vertical wire
>>> result = await add_wire(
...     start=(100.0, 100.0),
...     end=(100.0, 150.0)
... )

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end`	Yes
`start`	Yes

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

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says a wire is created and returns a dictionary with success status, but says nothing about permissions, whether the operation is reversible, error behavior for overlapping/duplicate wires, or side effects on existing nets. For a mutation tool with zero annotation coverage this is a significant gap.

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

Conciseness3/5

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

The tool intent is front-loaded, which is good, but the first two sentences are redundant restatements ('Add a wire between two points' / 'Creates a wire connection between start and end points'), and the two near-identical examples add little. The Args/Returns structure is orderly but partly wastes space.

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?

An output schema exists, so return values are covered, and both parameters are explained. But with no annotations and no usage guidance relative to overlapping siblings like add_bus_wire and connect_components, the definition is only minimally complete for an agent choosing between tools.

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% – the schema only shows two 2-element numeric arrays with no meaning. The description compensates well by naming both parameters, giving their format as an (x, y) tuple, and specifying units in mm, which the schema does not convey.

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 states a specific verb and resource ('Add a wire between two points', 'Creates a wire connection between start and end points') and clarifies the domain purpose ('connect component pins and establish electrical nets'). However, it never distinguishes itself from close siblings like add_bus_wire or connect_components, leaving the agent to infer the boundary.

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?

There is no explicit when-to-use guidance or exclusion criteria. Given siblings such as connect_components and add_bus_wire that overlap semantically, the description should say when a plain wire is appropriate versus those alternatives, but it offers nothing.

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