Skip to main content
Glama
Reid-n0rc

Future Electronics MCP

by Reid-n0rc

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FUTURE_API_KEYYesFuture Electronics API license key used in the x-orbweaver-licensekey header. Never commit this.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
future_lookup_partA

Look up one electronic component in the Future Electronics catalog by manufacturer part number (MPN). Returns a compact JSON summary: lookup_value, lookup_results, total_offers (offers found before truncation), and up to max_offers offers. Each offer lists MPN, Future part number, product URL, stock (quantity_available, quantity_on_order), minimum and order multiple, lead time, currency, price breaks, package type, MPQ, RoHS, date code, and datasheet URL when known. When quantity is given, each offer also has price_at_quantity: the price break that applies to that quantity, or a reason there is none (below_minimum, no_pricing, no_matching_break). Pricing matches the Future website and is NOT an official quote: Pricing is not an official quote. Confirm price and availability with Future Electronics before ordering. lookup_type defaults to exact, which matches the full part number. Use starts_with when you know only the beginning of the MPN (for example a base part without its packaging or temperature suffix), and contains when you know a fragment from the middle. Those return more, less precise offers, so check the mpn of each result. Set raw to true only when you need upstream fields the summary omits; it returns the untouched API response (offers still truncated to max_offers) and ignores quantity. Output is compact JSON capped at FUTURE_MAX_OUTPUT_TOKENS: if offers must be dropped to fit, the last ones go and truncated {omitted, hint} says how many. For many parts at once, use future_lookup_parts instead.

future_lookup_partsA

Look up many Future Electronics parts at once, e.g. a whole bill of materials (BOM). Accepts up to 2000 part numbers, each optionally with a quantity. Part numbers are trimmed and de-duplicated case-insensitively (quantities of duplicates are summed), then sent in batches of 300, several batches in parallel. Each part is judged on its best offer (the most stock) at the requested quantity (1 when none is given). By default it returns exceptions and totals, not every part: totals (requested, unique, found, not_found, errors, not_attempted, short_stock, below_moq, call_for_leadtime, batches, rate_limited), extended_cost (quantity x applicable unit price, summed per currency), unpriced (found parts with no applicable price break, left out of extended_cost), max_lead_time, and an issues table {columns, rows} listing ONLY problem parts. Problems: short_stock (available < quantity), below_moq (a given quantity < the minimum order), call_for_leadtime (lead time "CALL"), not_found, error, not_attempted; one part can have several, joined by ";" in its reason. Parts with no problem appear only in the counts. detail "all" returns a parts table with a row for every part instead. Output is capped at FUTURE_MAX_OUTPUT_TOKENS: when rows are dropped, truncated {omitted, hint} says so. If one batch fails, its parts get the error and the rest are still returned. If the API rate limit is still hit after retries, the lookup stops early: batches already running finish, and parts in batches not yet started are "not_attempted" (retry them later; totals.rate_limited is true). Prices are not an official quote. Use the single-part lookup tool for full offer details of one part.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: future_lookup_part for a single part with full offer details, and future_lookup_parts for bulk/BOM lookups. The descriptions explicitly guide the agent to use the correct tool for each scenario, eliminating ambiguity.

Naming Consistency5/5

Both tools follow a consistent snake_case pattern with the 'future_lookup_' prefix. This is predictable and easy to understand.

Tool Count4/5

Two tools cover the core lookup operations (single and bulk) well, which is appropriate for a focused catalog lookup service. However, the count is on the lower side compared to typical servers, making it slightly thin.

Completeness5/5

The server provides complete coverage for its apparent domain of electronic component lookup: single-part detailed lookup and bulk BOM processing with exception handling, totals, and pricing. No obvious gaps exist for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessResponsive