Skip to main content
Glama

sheetsdata-mcp

by io.github.octoco-ltd

find_alternative

Read-onlyIdempotent

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • changedInput schema / properties / constraints / default
      Previous value: -""New value: +[]
    • changedInput schema / properties / constraints / description
      Previous value: -"Optional constraints: 'in_stock' (only parts in stock), 'same_package' (must match package), 'jlcpcb' (available at JLCPCB). Comma-separated."New value: +"Optional 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)."
    • addedInput schema / properties / constraints / items
      Added value: +{
+  "enum": [
+    "in_stock",
+    "same_package",
+    "jlcpcb"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / constraints / type
      Previous value: -"string"New value: +"array"
    • changedInput schema / properties / limit / description
      Previous value: -"Max alternatives to return (default 5)"New value: +"Max alternatives to return (default 5, max 20)."
    • addedInput schema / properties / limit / maximum
      Added value: +20
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark the tool as read-only/idempotent/non-destructive. The description adds substantial behavioral context: filters out eval boards and dev kits, fuzzy package matching, fallback to semantic search, a 'hint' field, and exhaustive datasheet status handling. No contradiction with annotations.

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 long but well-organized with labeled sections and front-loaded core purpose. The datasheet status block is verbose, but it is directly relevant to interpreting returned matches and justifies its length. No filler sentences.

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?

No output schema exists, so the description carries the responsibility of explaining return values. It does so: match_score, match_notes, hint field, and datasheet statuses are all described. It also covers edge cases, fallback behavior, and when not to use the tool, making it self-sufficient.

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 parameters are already documented. The description adds value by explaining fuzzy matching behavior for 'same_package' and showing realistic usage via the constraints example. It does not fully explain 'limit' or 'part_number' beyond what schema provides, but the addition is meaningful.

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: 'Find alternative / second-source components for a given MPN.' It clearly states what the tool does and distinguishes it from siblings by mentioning search_parts for browsing and compare_parts for direct comparison.

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?

Dedicated 'When to use' and 'When NOT to use' sections explicitly name alternatives (search_parts, compare_parts) and give concrete scenarios (out of stock, cheaper equivalent, drop-in replacement). Even includes a usage example with constraints.

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

All sheetsdata-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search_parts finds parts, search_datasheets searches extracted content, read_datasheet reads sections, analyze_image extracts visual data, compare_parts batches comparisons, find_alternative finds substitutes, check_design_fit validates specs, prefetch/check/manage extraction status, and request/confirm handle uploads. The descriptions cross-reference each other to further eliminate ambiguity.

Naming Consistency5/5

All 12 tools follow the verb_noun snake_case pattern consistently (analyze_image, check_design_fit, compare_parts, prefetch_datasheets, request_datasheet_upload, etc.). No mixing of camelCase, verb styles, or vague generic names.

Tool Count5/5

12 tools is ideal for a datasheet-centric server, covering the full workflow from part discovery and datasheet extraction to analysis, validation, comparison, and upload. The count is neither bloated nor thin, and every tool earns its place.

Completeness5/5

The tool surface is comprehensive for the domain: part search, spec-based semantic search, detailed part data, datasheet reading (section/search), image analysis, design-fit checking, part comparison, alternative finding, extraction lifecycle management, and manual datasheet upload (request+confirm). No obvious dead ends or critical missing operations.

Resources