Skip to main content
Glama
hw-components-mcp

hw-components-mcp

by xt-mahh

Find Alternatives

find_alternatives

Find official alternative and replacement parts for an LCSC component by product ID to identify substitutes when a part is unavailable or needs comparison.

Instructions

查询元器件的官方替代料/替换料(当前仅 LCSC 支持,来自详情接口 alternatePartList)。

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": "find_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo仅 lcsc 支持替代料数据。lcsc
product_idYesLCSC C 编号(如 C8734)。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description has to carry the behavioral burden. It discloses the underlying source (alternatePartList) and the platform limitation, which is meaningful behavior beyond the schema, but it does not say whether it is read-only, what an empty result means (no alternates vs unsupported platform), or whether results are cached/rate-limited.

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 that front-loads the resource and parenthetically carries both the platform caveat and the data source. Nothing is redundant, though the parenthetical packs two ideas together.

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?

The tool is simple: two parameters, one required, with a full schema and an output schema, so return values need not be described. The description covers the one non-obvious constraint (LCSC only) and the data provenance, leaving only minor gaps around empty-result semantics.

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 the schema already documents both platform and product_id, including the C-number example. The description only reinforces the platform constraint. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (官方替代料/替换料 for a component), and it also identifies the data source (detail API's alternatePartList). This distinguishes it from sibling get_component_detail, though it does not explicitly state the relationship. The purpose is clear without opening the schema.

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?

The description states a hard constraint (currently only LCSC is supported), which is useful usage context, but it does not say when to prefer this tool over get_component_detail or what to do when a non-LCSC product_id is passed. Usage is implied rather than spelled out.

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