ICBOMS MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| icboms_search_componentsA | Search electronic components, microcontrollers, semiconductors, and passives across the ICBOMS catalog by MPN or keyword. |
| icboms_get_product_factsA | Get verified electrical specifications, package information, manufacturer, and lifecycle facts for a specific MPN from ICBOMS. |
| icboms_compare_partsA | Compare parametric specifications and check pin-to-pin or drop-in alternates between 2 to 8 electronic components. |
| icboms_procurement_rfqC | Get turnkey BOM procurement, Shenzhen component stock verification, and international DDP delivery instructions. |
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 4 tools
Each tool serves a clearly distinct function: searching, retrieving detailed facts, comparing components, and handling procurement. There is no overlap in their purposes, so an agent can reliably choose the correct tool for a given task.
All tools share the 'icboms_' prefix and most follow a verb_noun pattern (search_components, get_product_facts, compare_parts). The exception is 'procurement_rfq', which uses a noun_noun structure, creating a minor inconsistency that still remains understandable.
With only 4 tools, the server is tightly scoped and each tool is essential to the component lifecycle (search, detail, compare, procure). This is well within the ideal range and does not feel sparse or overloaded.
The tool set covers the main workflows for electronic component sourcing: discovery, specification retrieval, comparison, and procurement. A minor gap is the lack of an explicit list or batch operation for managing BOMs, but this is not a critical absence for the stated domain.