Skip to main content
Glama

BeaconMFG – China Supplier Directory

list_industries

列出国标小类「货架」:只列名录里已有企业的类,附该类全库企业条数。用户原话跟任何类名都对不上字、或 suggest_filters 没给出可靠候选时,用它按语义自己挑码。 可传 keyword 按类名/码子串筛,parent 按门类字母(C)/大类(35)/中类(348)/小类(3484) 前缀缩小。挑 1~3 个 code 后调 search_vendors(gb=) 验证。 ⚠ 远端轻量版:内嵌精简货架,不含 5.9MB 完整 industry-index.json;industries[].records 是全库该类企业总数,不是本次匹配数,也不是本轮 city 范围内的条数。⚠ 纯计算工具:不取企业记录,不消耗记录额度(但仍计入 IP 操作数)。

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_industries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数 1-200
offsetNo分页偏移
parentNo可选,门类字母(C) 或 大类(01)/中类(014)/小类(0141) 码前缀
keywordNo可选,类名 / 国标码 / 门类路径的子串,如「酒」「014」「C」

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses the lightweight remote edition lacking the full industry-index.json, explains that industries[].records is the全库 total rather than the match count or city-scoped count, and states the tool is pure computation that does not consume record quota but does count toward IP operations.

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?

Front-loads the core purpose, then the when-to-use rule, then warnings. Dense but nearly every sentence carries operational value; the ⚠ markers and bolding add noise that isn't strictly needed for an agent reader.

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

Completeness5/5

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

No output schema exists, yet the description explains the return shape (industries[].records), its meaning, quota implications, and the documented scope limitation of the lightweight index. For a 4-parameter, zero-annotation read tool, nothing an agent needs in order to call it correctly is missing.

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 the schema already documents limit, offset, parent, and keyword with examples. The description restates the same filtering semantics (name/code substring, parent prefix narrowing) without adding syntax or edge-case meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: list GB industry small categories that already contain enterprises, with per-category enterprise counts. It also distinguishes itself from suggest_filters and from search_vendors, which is the downstream consumer of the codes it returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('用户原话跟任何类名都对不上字、或 suggest_filters 没给出可靠候选时') and an explicit next step ('挑 1~3 个 code 后调 search_vendors(gb=<code>) 验证'). The alternative (suggest_filters) and the condition that selects this tool are both named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.