Skip to main content
Glama
hw-components-mcp

hw-components-mcp

by xt-mahh

Check Bom

check_bom

Batch-checks multi-line BOMs across LCSC, JD, and HQCHIP, returning stock, quantity-based pricing, and shortages per part to identify supply gaps before ordering.

Instructions

BOM 批量核查:多行「料号 数量」,逐行返回各平台库存、按量单价与缺口。

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": {
      "bom_lines": "<bom_lines>"
    },
    "name": "check_bom"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNolcsc / jd / hqchip / all(聚合多平台时每行含各平台结果)。lcsc
bom_linesYes多行文本,每行 "MPN 数量"(数量可省略,默认 1);# 开头为注释。

Output Schema

NameRequiredDescriptionDefault
linesNo
platformYes
total_linesYes
matched_linesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return content (per-platform stock, tiered pricing, shortage) and the input convention, but says nothing about how unmatched or ambiguous MPNs are handled, whether the call is read-only, or any rate/limit behavior.

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?

A single dense sentence that front-loads the operation, then the input format, then the output. No filler and nothing redundant.

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

Completeness4/5

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

With an output schema present, the description need not explain return values, and it still summarizes them. It covers the input format and platform aggregation adequately; the main gap is error/edge-case behavior for unresolvable part numbers.

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 coverage is 100%, so both parameters are already documented, including the platform enum values and the '#' comment convention. The description restates the line format rather than adding new meaning, so the 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?

The description names a specific verb and resource (BOM 批量核查) and states both the input shape (multi-line '料号 数量') and the per-line output (各平台库存、按量单价与缺口). This clearly separates it from single-part siblings like search_components or get_component_detail, though it never names an alternative explicitly.

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?

Usage is only implied: the batch, multi-line framing suggests it is for checking a whole BOM at once rather than one part. There is no explicit when-to-use/when-not guidance and no pointer to siblings for single-part lookups.

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