Skip to main content
Glama
Copper

Copper

Import part

parts_import
Idempotent

Makes a provider part usable in a KiCad project by returning its lib_id and footprint for schematic placement, with options to inspect the symbol/footprint or force stock/provider sources.

Instructions

Make a provider's part usable in this project: returns the lib_id + footprint for sch_apply place. sch_apply {"op":"place","part":...} calls this by itself; use it directly to inspect a part first or to force a source. prefer='auto' (default) uses KiCad's stock symbol + footprint when it verifiably fits, else converts the provider's symbol, footprint and 3D model into project libraries (registered in the project's lib tables); 'easyeda' forces the provider's drawing, 'stock' fails if there is no stock fit. Footprint pads are checked against symbol pins and KiCad itself loads the result. preview=true returns pictures of the symbol and footprint. Example: parts_import(part='C165948')

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "parts_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
lcscNoshorthand for part=<C-number>, provider='lcsc'
partNothe provider's part number
preferNolcsc only
previewNoattach a PNG (default false)
projectNoproject path (default: active)
with_3dNodownload/convert the 3D model (default true)
providerNoparts provider to ask (default: the project's parts.providers, in order): lcsc | local | kicad | a third-party name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations for an open-world, idempotent, non-destructive operation, the description discloses real side effects: converting the provider's symbol/footprint/3D model into project libraries and registering them in the project's lib tables, plus validation (pads checked against pins, KiCad loads the result) and the preview behavior. It also states the failure mode of prefer='stock'. That is substantial behavioral detail not carried by structured fields.

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?

Front-loaded and dense with useful content; the return value and the default dispatch behavior come first, followed by the mode semantics. There is mild redundancy and an awkward trailing 'sch_apply' fragment, but no sentence is clearly disposable.

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?

There is no output schema, and the description compensates by describing the return value (lib_id + footprint) and the preview output. For a 7-parameter tool all parameters are documented in the schema, and the main risk surfaces (library registration, validation, stock failure) are covered. Minor gap: the provider fallback ordering and project defaulting are only in the schema.

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?

With 100% schema coverage the baseline is 3, but the description adds real semantics for the enum values of prefer and for preview (attaches pictures of symbol and footprint). It leaves with_3d, project, provider fallback ordering and the lcsc shorthand entirely to the 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 uses a concrete, specific verb and resource: 'Make a provider's part usable in this project', and immediately states the output ('returns the lib_id + footprint for sch_apply place'). By naming sch_apply as its consumer, it also distinguishes this tool from parts_search/parts_get, which work differently, so an agent can tell them apart without reading any schema.

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?

The description clearly says when to call the tool directly ('to inspect a part first or to force a source') and notes that sch_apply calls it automatically when placing a part. It also gives each prefer mode a condition ('auto' when stock verifiably fits, 'easyeda' to force the provider drawing, 'stock' to require a stock fit). It never explains when to prefer parts_get or parts_alternatives, so this is not a full when/when-not discussion.

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