Skip to main content
Glama

BeaconMFG – China Supplier Directory

get_capability_card

取某家企业的能力卡(结构化工艺/设备/认证/产能证据,比 get_vendor 的档案更适合做「这家到底能不能做」的判断)。输入是 search_vendors 返回的 8 位 token。返回 found:false 表示这家暂无已发布的能力卡(不是错误)。

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses what the card contains (structured evidence across process, equipment, certification, capacity) and, importantly, that found:false is a legitimate empty state rather than an error — a real behavioral nuance. It does not explicitly say the call is read-only or whether access is restricted per company, which is the remaining gap.

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?

Three compact sentences, front-loaded with the resource, then the sibling comparison, then input and the empty-result caveat. The parenthetical enumeration is dense but earns its place by telling the agent what evidence to expect.

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?

A single-parameter read tool with no output schema; the description compensates by naming the evidence categories returned and handling the found:false case. Only the broader return shape and any access constraints are left implicit, which is minor at this complexity.

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 parameter description already states it is the 8-digit subject token from search_vendors hits[].id. The description restates the same origin information, so it adds validation of the format but no new meaning beyond the schema.

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 (取/get) and resource (能力卡/capability card), and immediately qualifies the resource as structured process/equipment/certification/capacity evidence. It explicitly contrasts itself with the sibling get_vendor, so an agent can choose between the two without opening either schema.

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?

Gives clear selection guidance: use this over get_vendor when the question is "can this company actually do the work". It also explains where the input token comes from (search_vendors). It stops short of stating when get_vendor would still be the better pick, so it is directional rather than exhaustive.

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.