Skip to main content
Glama
ethan-hub26

embedcalc-mcp

by ethan-hub26

Find Real Component (MPN + buy link)

embedcalc_find_component
Read-only

Search for in-stock electronic components by type and electrical value, returning manufacturer part numbers and direct buy links. Filters include tolerance, power, voltage, current, and more.

Instructions

Find real, in-stock components matching an electrical value via parametric distributor search — returns manufacturer part numbers and buy links ONLY (no price or stock data, by design).

Args:

  • type: resistor | capacitor | inductor | ldo | mosfet | bjt.

  • value (number): resistor: resistance in ohms; capacitor: capacitance in farads (e.g. 1e-7 = 100 nF); inductor: inductance in henries (e.g. 1e-5 = 10 µH); ldo: fixed output voltage in volts; mosfet: minimum Vds rating in volts (N-channel); bjt: minimum Vce rating in volts (NPN).

  • Optional filters: tolerance_pct (R/C/L: keep this tolerance or tighter), min_power_w (resistor), min_voltage_v (capacitor rating), min_current_a (ldo/mosfet/bjt), max_rds_on_ohm (mosfet), min_hfe (bjt).

  • max_results (default 5).

Returns (structured): { matched_value, parts: [{ mpn, manufacturer, description, buy_url }] }. For prices, follow the buy link — pricing is intentionally not returned.

Examples:

  • "220 ohm 1% resistor" -> type='resistor', value=220, tolerance_pct=1

  • "100 nF cap rated 16V+" -> type='capacitor', value=1e-7, min_voltage_v=16

  • "3.3V LDO, 500 mA" -> type='ldo', value=3.3, min_current_a=0.5 Requires internet access (queries embedcalc.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesComponent type
valueYesPrimary value — meaning depends on type (ohms / farads / henries / volts)
min_hfeNoMinimum hFE / current gain (bjt)
max_resultsNoMaximum parts to return
min_power_wNoMinimum power rating in watts (resistor)
min_current_aNoMinimum current in amps (ldo output / mosfet Id / bjt Ic)
min_voltage_vNoMinimum voltage rating in volts (capacitor)
tolerance_pctNoMax tolerance in % (resistor/capacitor/inductor)
max_rds_on_ohmNoMaximum Rds(on) in ohms (mosfet)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
partsYes
matched_valueYesThe parametric value string the search matched
Behavior4/5

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

Discloses internet requirement, intentional omission of pricing, and dependent parameter meanings. Aligns with annotations (readOnlyHint, etc.) 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with Args, Returns, and Examples sections. Front-loaded with purpose, no redundant 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?

Covers all essential aspects: purpose, parameters with examples, output format, and behavioral notes. Annotations and schema complement completeness.

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?

Adds significant meaning beyond 100% schema coverage, especially for the 'value' parameter and filter parameters with type-specific explanations and examples.

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: finding real, in-stock components via parametric search and returning MPNs and buy links. It specifies component types and distinguishes itself from sibling calculation tools.

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?

Provides clear usage context with examples and notes on intended use (e.g., no pricing). Lacks explicit when-not-to-use or alternatives, but sibling tools are all different calculation utilities.

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/ethan-hub26/embedcalc-mcp'

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