Skip to main content
Glama

find_alternative

Read-onlyIdempotent

Find alternative electronic components for a given MPN. Get ranked matches with specs, package, and availability, filtered by stock or footprint.

Instructions

Find alternative / second-source components for a given MPN. Returns parts ranked by how closely their specs, package, and category match the reference part, with a match_score and match_notes explaining each match.

When to use:

  • Original part is out of stock or end-of-life.

  • You need a cheaper equivalent with similar specs.

  • You need a second source for supply-chain resilience.

  • You need a drop-in replacement on an existing PCB (use constraints=['same_package']).

When NOT to use:

  • You're browsing a category from scratch — use search_parts.

  • You already have candidates and want a head-to-head comparison — use compare_parts directly.

Behavior:

  • Eval boards, dev kits, and breakout modules are filtered out — results are IC-level alternatives only.

  • 'same_package' uses fuzzy matching, so SOT-23 ≡ SOT23, SOIC-8 ≡ SOP-8, LQFP64 ≡ TQFP64, etc. Exact string match is not required.

  • If provider search returns few candidates, the tool falls back to semantic search across extracted datasheets to surface niche alternatives.

  • The response includes a 'hint' field pointing to compare_parts / read_datasheet for drilling into promising alternatives.

Example: find_alternative('TPS54302', constraints=['same_package', 'in_stock'])

DATASHEET STATUS VALUES:

  • 'ready' — extracted and indexed; call read_datasheet, search_datasheets, or analyze_image.

  • 'extracting' / 'in_progress' / 'queued' / 'pending' — extraction running or scheduled. Poll check_extraction_status every 5-10s until 'ready' or 'failed'. Typical time: 30s-2min.

  • 'not_extracted' — known part but datasheet hasn't been fetched yet. Trigger it via prefetch_datasheets (cheapest) or by calling read_datasheet (auto-triggers on first read).

  • 'no_source' — we couldn't find a public datasheet URL for this MPN. First, retry prefetch_datasheets in 10-30s (the URL resolver re-runs and often finds a source on the second pass). If still 'no_source', the agent can upload the PDF manually via request_datasheet_upload + confirm_datasheet_upload (see those tools). Org-uploaded datasheets are private to the org.

  • 'unsupported' — PDF exists but can't be extracted (scanned image-only, encrypted, or corrupted). Upload a clean text-based PDF via request_datasheet_upload to override.

  • 'failed' / 'error' — extraction errored. The response includes the error reason. Retry via prefetch_datasheets or escalate to support.

  • 'rejected' — input wasn't a real MPN (bare value like '100nF', description, or reference designator). Fix the input and re-call.

  • 'deduplicated' — another part in the family already has this datasheet; same content is returned under the primary MPN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax alternatives to return (default 5, max 20).
constraintsNoOptional filters to narrow alternatives. 'in_stock' = only parts with non-zero stock at any provider. 'same_package' = package footprint must match (fuzzy). 'jlcpcb' = must be available at JLCPCB (useful for JLCPCB-assembled boards — also restricts the provider search to JLCPCB).
part_numberYesThe MPN to find alternatives for
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: filtering of eval boards, fuzzy matching for packages, fallback to semantic search, and inclusion of a 'hint' field. Annotations already indicate readOnly=true, openWorld=true, idempotent=true, and destructive=false, and the description adds significant context without contradiction.

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 description is well-structured with sections but includes a large block on datasheet status codes that is not directly relevant to the tool's primary function. This extraneous detail harms conciseness. The main behavioral description is clear and front-loaded.

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?

Given the tool has 3 parameters and no output schema, the description provides sufficient context about the output format, behavior, and edge cases. The inclusion of datasheet status codes is excessive but does not detract from completeness. A more focused description would improve this score.

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?

All three parameters are documented in the input schema with descriptions. The description adds value by explaining the constraints options ('in_stock', 'same_package', 'jlcpcb') and providing an example usage. However, schema coverage is already 100%, so the incremental value is moderate.

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 clearly states the tool's function: 'Find alternative / second-source components for a given MPN.' It specifies the output (ranked parts with match_score and match_notes) and distinguishes it from siblings like search_parts and compare_parts through explicit usage guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use scenarios (out of stock, cheaper alternative, supply chain resilience, drop-in replacement) and when-not-to-use conditions (browsing categories or having candidates). It also includes a concrete example and explains how constraints like 'same_package' should be used.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/octoco-ltd/sheetsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server