Skip to main content
Glama
Copper

Copper

Part alternatives

parts_alternatives
Read-onlyIdempotent

Find in-stock substitutes for out-of-stock or expensive parts by part number or spec, then apply the chosen alternative.

Instructions

In-stock substitutes for a part — use when a part is out of stock, in a dear assembly class (JLC Extended: ~$3 setup fee), or too expensive. target: a part number (→ same package, same value / same MPN family; for lcsc Basic > Preferred > Extended, then stock) or a free-text spec ('100nF 0402'). For ICs the alternatives are the same MPN family from other makers/packagings — check the datasheet pinout before swapping. Apply with sch_apply set_field (the result's next gives the op). Example: parts_alternatives(target='C15401')

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

Input Schema

NameRequiredDescriptionDefault
lcscNoalias of target for an LCSC C-number
limitNomax results (default 8)
targetNopart number (e.g. 'C15401') or spec ('100nF 0402')
providerNoparts provider to ask (default: the project's parts.providers, in order): lcsc | local | kicad | a third-party name
same_packageNodefault true

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?

Goes well beyond the readOnly/openWorld/idempotent annotations: it discloses the LCSC ranking policy (Basic > Preferred > Extended, then stock), the substitution-equivalence rules for passives vs ICs, an explicit safety caveat to check the datasheet pinout before swapping, and where the next operation appears in the result (`next`). That is real behavioral context an agent cannot get from the 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 with the triggering condition and uses a labeled 'target:' clause plus a concrete example, so it scans well. It is dense with parentheticals and could shed a clause or two without losing meaning.

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?

With no output schema, the description compensates by pointing at the result's `next` field and by explaining ranking and substitution risk. Remaining gaps (pagination via limit, provider fallback order behavior when a provider fails) are minor and mostly covered by 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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining what target resolution actually does (same package, same value / same MPN family) and how provider selection is ranked, which the schema does not convey. limit, provider and same_package semantics are left 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?

States a specific verb and resource — in-stock substitutes for a part — and immediately frames the scope as substitution rather than general search, which separates it from siblings like parts_search and parts_get.

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?

Gives three explicit triggers (out of stock, JLC Extended ~$3 setup fee, too expensive) and closes the loop with the follow-up action via sch_apply set_field. It doesn't name a competing sibling or state when not to use it, which keeps it short of a 5.

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