Skip to main content
Glama

BeaconMFG – China Supplier Directory

get_vendor

按主体 id 取完整中文档案。字段:company(名称)、address(地址)、lat/lng(坐标)、contact_phone(电话)、category(行业路径)、keywords(关键词)、region(省市区)、source/source_url(来源)、verified_at/last_verified_at(核验时间)。id 用 search_vendors 返回的那个 8 位 token。若这家已归集到政府主体,回执里多一个 linked_entity:{uscc 统一社会信用代码, legal_name 法定登记名称, relation, origin, score}。company 是经营招牌名,linked_entity.legal_name 是工商登记名,两者经常不同;签约、开票、查资质一律用 legal_name + uscc。取多家请多次调用(每次一条计一次额度,重复看同一家不重复计)。

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": {
      "id": "<id>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes8 位主体 token,来自 search_vendors 的 hits[].id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, yet the description carries a lot of the burden: it discloses quota behavior (one call = one unit, repeat views of the same entity are not double-charged) and a conditional response shape (linked_entity only appears when the vendor maps to a government entity). It omits explicit read-only/auth framing, but the quota and conditional-field disclosure are substantial value beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then the field list, then the conditional linked_entity semantics, then quota rules — no sentence is filler. The long field enumeration is justified because there is no output schema to convey return contents.

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?

With no output schema, the description takes responsibility for describing return fields, the conditional linked_entity object and its subfields, and a critical semantic distinction between company (trade name) and legal_name (registered name) with guidance to use legal_name + uscc for contracts. Combined with the quota note, an agent has everything needed to call and interpret the result correctly.

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% for the single required parameter, and the schema already states the id comes from search_vendors hits[].id, so the description's restatement adds no new syntax or format detail. Baseline 3 is appropriate when the schema fully documents the only parameter.

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?

Opening clause states a specific verb and resource ('按主体 id 取完整中文档案') and the description immediately ties the tool to search_vendors as the id source, so an agent can distinguish it from the sibling search tool without opening the schema. The enumerated field list confirms exactly what '完整档案' means.

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

Usage Guidelines4/5

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

It gives clear operating context: the id must be the 8-digit token returned by search_vendors, and multiple entities require multiple calls. It does not state exclusions (e.g. when to prefer get_capability_card), but with a single-param lookup tool the intended use case is unambiguous.

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.