Skip to main content
Glama
electronic-components-mcp

electronic-components-mcp

by veronoicc

search_components

Find electronic components by keyword or part name across German and global retailers, filtering results by price, stock status, country, and limit.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to retrieve per shop (default 10)
queryYesSearch term, e.g. 'esp32', 'ne555', 'bme280', '10k resistor'
countriesNoOptional country/region filter, e.g. ['de'] for German stores only, ['global'] for overseas/global stores only. Default: all registered stores
max_priceNoMaximum price in EUR
min_priceNoMinimum price in EUR
in_stock_onlyNoOnly return items currently in stock

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • changedInput schema / properties / countries / description
      Previous value: -"Country/region codes, e.g. ['de'], ['global'], ['de', 'global']. Default: global only"New value: +"Optional country/region filter, e.g. ['de'] for German stores only, ['global'] for overseas/global stores only. Default: all registered stores"
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It does disclose meaningful behavior beyond the schema: that the call fans out across multiple external retailers (BerryBase, Reichelt, Mouser, AliExpress) and defaults to all of them, which signals a multi-source, network-bound operation. It says nothing about latency, rate limits, result aggregation/deduplication, or failure behavior when a shop is unreachable — gaps that matter for a fan-out search with zero annotation coverage.

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?

Two sentences, front-loaded with the verb and resource, with scope details after. The retailer enumeration is slightly verbose but earns its place by grounding the agent in the domain (German electronics retailers plus global marketplaces). No filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no annotations, and no output schema, the description covers the 'what and where' adequately but leaves the return shape entirely undefined — an agent cannot know whether results are per-shop lists, price/stock fields, or a flat array. For a fan-out search tool this is a noticeable gap, though all inputs are well covered by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (limit, query, countries, min_price, max_price, in_stock_only) is already documented with examples and defaults in the schema. The description adds only the 'keyword or part name' framing for query and the all-stores default, which largely restates schema content. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (electronic components) plus the scope of where it searches: registered online stores, with named examples. The phrase 'by keyword or part name' implicitly separates it from the sibling search_components_by_type, but that sibling is never named, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Default searches all stores' tells the agent the default scope and hints that narrowing is possible via the stores/region dimension. There is no explicit when-to-use versus when-not guidance, no mention of search_components_by_type or get_component_by_id as alternatives, and no prerequisites (e.g., whether shops must be registered via list_supported_shops first).

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