Skip to main content
Glama
hw-components-mcp

hw-components-mcp

by xt-mahh

List Platforms

list_platforms

Lists supported electronic component platforms with data notes on currency, stock basis, and regional/anti-scraping requirements, so agents can choose a source and interpret results correctly.

Instructions

列出可接入的元器件平台及数据说明(币种口径、库存口径、区域/反爬要求)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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 exist, so the description carries the full burden. It does disclose the substantive content of the response—per-platform currency basis, inventory basis, and regional/anti-scraping constraints—which is genuinely useful operational context for deciding whether a platform is usable. It does not state that the call is read-only, whether it requires credentials, or whether results are cached/static, so the behavioral picture is partial.

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 front-loaded sentence with the core action first and qualifications condensed into one parenthetical clause. Nothing is wasted, though the parenthetical is dense enough that it packs three distinct notions into one breath.

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?

For a parameterless listing tool with an output schema already present, the description needs only to say what is being listed and why it matters; it does both, and the return shape is covered by the output schema. The only gap is the absence of any note on auth or on how the platform list is scoped for the caller.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical instead enriches the tool's output semantics, which is a reasonable use of the space.

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 opens with a specific verb-and-resource pair ('列出可接入的元器件平台') and adds that each entry carries data-semantics notes (currency basis, stock basis, regional/anti-scraping requirements). That clearly separates it from the sibling lookup tools (search_components, get_component_detail), which operate on components rather than platform metadata, 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: an agent can infer this is the discovery/configuration call to make before querying components, since it enumerates supported platforms and their data conventions. There is no statement of when to call this versus another tool and no prerequisites or exclusions.

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