Skip to main content
Glama
hw-components-mcp

hw-components-mcp

by xt-mahh

Search Components

search_components

Search and compare electronic components by part number, LCSC C number, or keyword across LCSC, JD, and HQCHIP, returning unified results with stock filters and tiered pricing.

Instructions

按型号/关键词搜索元器件,返回统一格式结果列表。

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": {
      "keyword": "<keyword>"
    },
    "name": "search_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo每平台最多返回条数(1-50)。
keywordYes型号(如 STM32F103C8T6)、LCSC C 编号(如 C8734)或泛化描述(如 0603 10k)。
platformNolcsc(立创,数据最全)/ jd(京东)/ hqchip(华秋,人民币自营价)/ all(聚合三平台)。lcsc
in_stock_onlyNo仅保留有现货的结果。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it only notes that results come back in a unified format. It says nothing about querying multiple platforms, network/latency behavior, rate limits, or what happens when a platform yields no matches — all relevant for an aggregating search.

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?

A single compact sentence with the action front-loaded and no filler. It is efficient, though so terse that it borders on under-specification rather than being a model of structure.

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

Completeness2/5

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

With four parameters, an output schema, and no annotations, the description should at least explain the multi-platform aggregation behavior and how this differs from detail/alternative-lookup siblings. It covers only the bare purpose, leaving the agent to reconstruct the rest from schema fields.

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 (keyword, platform, limit, in_stock_only) is already documented with examples and defaults in the schema. The description adds no parameter-level meaning beyond that, which is the baseline-3 case.

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?

The description states a concrete verb and resource ("按型号/关键词搜索元器件") and adds an output promise ("返回统一格式结果列表"), so an agent knows it performs a keyword/part-number component lookup. It does not distinguish itself from siblings like get_component_detail or find_alternatives, which is what keeps it below a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. The only usage signal is the implied action of searching, so an agent must infer from sibling names alone whether to call this or get_component_detail/find_alternatives.

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