Skip to main content
Glama
hw-components-mcp

hw-components-mcp

by xt-mahh

Download Datasheet

download_datasheet

Downloads a component datasheet PDF for a given product ID, saves it locally, and returns the absolute file path for later PDF reading.

Instructions

下载数据手册 PDF 到本地并返回文件绝对路径(供后续用 pdf 工具精读)。

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

Input Schema

NameRequiredDescriptionDefault
platformNolcsc / jd / hqchip。lcsc
save_dirNo保存目录,默认 ./datasheets。./datasheets
product_idYesLCSC C 编号 / 京东 sku(京东通常无手册)/ 华秋 goodsId。

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?

No annotations are supplied, so the description carries the full burden. It does disclose the key side effect (a file is written to local disk and the absolute path returned), which is more than the schema says. But it is silent on overwrite behavior, whether downloads are rate-limited or authenticated, file size, and what happens when a product has no datasheet — a real case the schema hints at for JD skus but the description never addresses.

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 leads with the action and ends with the return value and its purpose — no filler. It is arguably slightly under-specified rather than verbose, but nothing is wasted.

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 (3 params, one required), an output schema exists, and the description still states what comes back (the absolute path). The only meaningful gap is failure behavior when no datasheet exists for a given product, which matters given the JD caveat in 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 product_id, platform, and save_dir are all already documented in the schema, including the per-platform ID formats and the default save directory. The description adds no meaning beyond that; 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 (下载 / download) and a specific resource (数据手册 PDF), and states the outcome (returns the file's absolute path). That is enough to distinguish it from search_components or get_component_detail, which surface metadata rather than fetching files, though it never names those siblings.

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?

It gives one downstream-usage cue — the path is meant for follow-up close reading with a pdf tool — which implies 'use this when you need the actual document, not just metadata.' However it never says when NOT to use it, nor does it route the agent to an alternative when a datasheet is unavailable.

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