Skip to main content
Glama
Copper

Copper

Part detail

parts_get
Read-onlyIdempotent

Get full details for a provider part number: LCSC/JLC stock, price ladder, datasheet, EasyEDA models, and KiCad import availability—check stock and sourcing before committing.

Instructions

Full detail for one part by its provider part number. The provider is found from the id (a C-number is LCSC; 'name:id' names one) or provider. lcsc: JLC assembly stock + Basic/Preferred/Extended class + price ladder + attrition (authoritative for JLC PCBA), LCSC retail stock (a different pool — labelled), parameters, datasheet URL, whether EasyEDA has a symbol/footprint/3D model, and whether parts_import would use a KiCad stock symbol+footprint or import from EasyEDA. Other providers: the catalogue record (mpn, manufacturer, value, package, stock, symbol/footprint, extra supplier fields). Use before committing to an unfamiliar part, or to check stock/class of a part already on the schematic. Example: parts_get(part='C2040')

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
lcscNoshorthand for part=<C-number>, provider='lcsc' (digits alone are accepted)
partNothe provider's part number, e.g. 'C25804' (LCSC) or an MPN from your catalogue
easyedaNolcsc: also check EasyEDA symbol/footprint availability (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.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses meaningful behavior: LCSC returns JLC assembly stock versus LCSC retail stock, class, price ladder, attrition, datasheet and EasyEDA model availability, and whether parts_import would use a KiCad stock symbol or EasyEDA import. It also explains that other providers return the catalogue record.

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 with the core purpose and then branches cleanly into lcsc versus other-provider return behavior. It is dense and semicolon-heavy in the LCSC sentence, but most detail earns its place because there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of explaining return values, and it does so comprehensively for both LCSC and other providers. It also covers provider resolution, EasyEDA checks, and the intended decision points for calling the tool.

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 coverage is 100%, so the schema already documents all four parameters. The description still adds useful meaning by explaining that the provider can be inferred from the id, that a C-number means LCSC, and that 'name:id' names a provider.

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 starts with a precise verb and resource: 'Full detail for one part by its provider part number.' It also scopes the tool to a single part, making it distinguishable from catalogue-search siblings, and explains provider resolution in concrete terms.

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 explicitly says to use it 'before committing to an unfamiliar part' or 'to check stock/class of a part already on the schematic.' That gives clear context, though it does not name when-not-to-use cases or explicitly route to alternatives such as parts_search.

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