Skip to main content
Glama

BeaconMFG – China Supplier Directory

get_onboarding_guide

给供应商「入驻 / 认领」入口:返回可直接点开的控制台链接与步骤,外加一条非手机 App 的 HTTP/JSON 自助通道说明(供供应商自己的 Agent 认领并上传资料)。 当用户说「我是某某公司的」「我想入驻/上架产品/让客户搜到我」「我要认领我的企业」「怎么注册成供应商」「我的审核到哪一步了」时调用。 ⚠ 本工具只给入口,绝不代办:短信验证码与法人手机核验必须由用户在自己的浏览器里输入 —— 让他把验证码念给你,等于把「证明他是这家企业」的凭证交给第三方,还会进入对话上下文与日志。 ⚠ 不要替用户编造企业信息,不要承诺审核结果或时效,也不要把未认领的企业说成「已经属于你」。

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

Input Schema

NameRequiredDescriptionDefault
intentNoclaim=认领已收录企业(默认);register=库里没有要新建档;status=查审核进度;agent=看 Agent HTTP 自助通道契约
companyNo可选。企业名称,用于把步骤说得更具体
supplier_idNo可选。已拿到的 8 位 token,用于生成直达深链

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 so well: it discloses that the tool is entry-point-only and performs no action on the user's behalf ("只给入口,绝不代办"), and explains the security rationale — a verification code spoken into chat becomes context and logs, undermining proof of company ownership. It does not describe response shape, pagination, or failure modes, which keeps it from a 5.

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-loaded with what the tool returns, then triggers, then constraints — a sensible order with no filler sentences. It is somewhat long and uses bold/emoji warning markers, but each warning covers a distinct hazard rather than repeating the schema.

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 zero-required-parameter guide tool with no annotations and no output schema, the definition covers purpose, invocation triggers, output content (links + steps + HTTP contract), and the key misuse hazards. A brief note on the actual response structure or what happens with an invalid supplier token would close the remaining gap.

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?

Schema description coverage is 100%, so the baseline is 3, but the description earns a bump by mapping its four trigger scenarios onto the intent enum (入驻/认领 → claim, 新建档 → register, 审核进度 → status, Agent 通道 → agent). It adds little about supplier_id beyond the schema's own note about generating a direct deep link.

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?

The description names a specific verb and resource — returning a supplier onboarding/claim entry point with clickable console links and steps, plus a non-app HTTP/JSON self-service contract. It also enumerates the exact user utterances that should trigger it, which makes it separable from data-lookup siblings like get_vendor or search_vendors without opening any 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?

Usage conditions are unusually explicit: a full list of trigger phrasings ("我想入驻/上架产品", "我要认领我的企业", "我的审核到哪一步了") and clear exclusions in the warning block (never enter SMS/legal-rep verification on the user's behalf, never fabricate company data, never promise review outcomes or timing). What is absent is any naming of sibling tools or statement of when to prefer get_vendor / search_vendors instead, so it stops short of a 5.

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.