copper-mcp

by seunghyukchoe

Overview Schema Source Related Servers Discussions Admin

Python

Local

render_circuit_schematic

Convert validated Circuit Intent content into a private, ephemeral KiCad schematic resource for inspection.

Instructions

Render validated Circuit Intent content into one private ephemeral KiCad resource.

``content`` must contain exactly ``circuit_id``, ``project_name``, ``title``,
``components``, ``nets``, and ``ports`` under Circuit Intent 0.1.0. Components
are two-pin resistors or non-polarized capacitors; nets carry explicit
component-pin connections and ports identify external nets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "render_circuit_schematic"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes	Advertised structured content for ``render_circuit_schematic``.

Output Schema

Name	Required	Description	Default
`intent`	Yes
`schema`	Yes
`status`	Yes
`artifact`	Yes
`verification`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations are all false, offering little safety guidance. The description does add 'private ephemeral' and 'validated', which indicate the resource is temporary and input must be pre-validated. However, it does not disclose what happens on invalid input, whether the operation is repeatable, or any side effects beyond creating the resource.

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 appropriately short—two sentences—with the primary action front-loaded. The second sentence is dense and lists required fields, but it is not overly verbose. A bit more structure (e.g., bullets) would improve readability, but it remains efficient.

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?

The tool has a rich output schema and detailed input schema, which reduces the need to describe return values. The description covers input format and resource type, but lacks guidance on validation flow or error behavior. Given the many sibling tools, some cross-referencing would improve completeness.

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?

Although schema coverage is high with descriptions on nested types, the description adds critical semantics: it specifies the exact required fields, the Circuit Intent version 0.1.0, and the allowable component types (two-pin resistors/non-polarized capacitors). This meaningfully complements the schema's structural definitions.

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 opens with a specific verb and resource: 'Render validated Circuit Intent content into one private ephemeral KiCad resource.' This clearly distinguishes the tool from board-focused siblings like inspect_board or preview_placement. The scope is explicit: it renders schematics only.

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 implies usage by focusing on Circuit Intent content and the render action, but it does not explicitly state when to choose this over alternatives or mention validation as a prerequisite. The sibling tools are board-focused, so context is implied rather than stated.

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

Deploy Server