electronic-components-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_componentsB | Search electronic components across registered online stores (German retailers like BerryBase, Reichelt, Conrad, Mouser, etc., and global stores like AliExpress) by keyword or part name. Default searches all stores. |
| search_components_by_typeB | Search electronic components by structured component category and optional ratings/specs across registered online stores. Default searches all stores. |
| get_component_by_slugB | Retrieve exact component details using a composite slug |
| get_component_by_idB | Retrieve component details using a specific store identifier and store's internal item ID |
| list_supported_shopsA | List all registered electronic component stores with their shipping policies and supported regions |
| cart_add_itemC | Add an electronic component to the store shopping cart |
| cart_update_itemA | Update the quantity of an item in the shopping cart (0 to remove) |
| cart_remove_itemB | Remove an item completely from the shopping cart |
| cart_set_shipping_methodC | Select a specific shipping or pickup method for a store cart (e.g. "pickup", "dhl", "ups_express") |
| cart_viewB | View the current shopping cart with shipping costs, pickup locations, free shipping thresholds, and grand totals |
| cart_clearB | Clear items from shopping cart for a specific shop or all shops |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target clearly distinct operations, especially cart actions versus component lookup. The main overlap is between the two search tools (keyword vs structured type) and the two get-component tools (ID vs slug), plus cart_update_item with quantity 0 versus cart_remove_item, but descriptions make these mostly distinguishable.
Names are consistently snake_case and mostly follow a predictable verb/resource pattern such as search_components, get_component_by_id, and list_supported_shops. The cart_* namespace is coherent, though cart_view and cart_clear put the resource before the verb, a minor deviation from the otherwise verb-first style.
With 11 tools, the set is well-scoped for an electronics search and shopping-cart assistant. Search, lookup, shop listing, and cart lifecycle operations each have a clear role without excessive granularity.
The surface covers component search, exact component lookup, supported shop discovery, and a fairly complete cart lifecycle including shipping method selection and clearing. The obvious missing operation is checkout/order placement, though that may be intentionally out of scope or handled on the retailer site.