Skip to main content
Glama
hw-components-mcp

hw-components-mcp

by xt-mahh

Get Component Detail

get_component_detail

Retrieves complete details for a component by product ID—parameters, tiered pricing, stock, MOQ, datasheet link, and alternatives—across LCSC, JD, and HQCHIP.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_component_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNolcsc / jd / hqchip。lcsc
product_idYes平台商品编号 —— LCSC 为 C 编号(如 C8734),京东为数字 sku,华秋为数字 goodsId。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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; '获取' implies a safe read but the description never states it explicitly, nor does it mention failure modes (unknown product_id, unsupported platform) or any rate/permission constraints. It does at least disclose the payload contents, though with an output schema present that is largely redundant.

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?

One front-loaded sentence with no filler; the field list is a compact payload summary. Slightly wasted given the output schema already lists those fields.

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?

Adequate for a simple 2-parameter lookup whose return shape is covered by the output schema, but it leaves an agent without guidance on platform default behavior, error handling, or when a sibling tool is the better call.

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% and both parameters are documented in-schema, including the platform-dependent ID format, so the description adds nothing beyond it. 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 and resource ('获取元器件完整详情') and enumerates the detail fields returned, which separates it from a plain search tool. It stops short of naming or contrasting any sibling such as download_datasheet or find_alternatives, which cover overlapping data.

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: nothing says this is the follow-up call after search_components or that it should be used instead of the datasheet/alternatives tools. The only usage signal is implicit in the word 'detail'.

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