Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

统一社会信用代码校验

cn-uscc

统一社会信用代码校验:输入 18 位统一社会信用代码,返回是否符合 GB 32100-2015(校验位是否通过)、登记管理部门、行政区划码、主体标识码。企业主体核验、发票抬头校验、供应商准入的第一步。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "input": "<input>"
    },
    "name": "cn-uscc"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes18 位统一社会信用代码

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does reasonably well: it implies a pure, side-effect-free computation ('返回确定性计算结果与依据'), names the governing standard GB 32100-2015, and discloses the check-digit logic. It stops short of explicitly stating it is read-only and non-persistent, which would have made this a 5 for an unannotated tool.

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

Conciseness3/5

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

The purpose and return fields are front-loaded, but the tail contains filler: '传入参数对象,返回确定性计算结果与依据' restates the obvious, and the '适用场景' sentence overlaps with the earlier scenario list. Tightening these would remove redundancy without losing information.

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 single-parameter validator with no output schema, the description helpfully enumerates the returned fields, which compensates for the absent output schema. Only the failure-path behavior (e.g., what is returned for a malformed or non-18-character input) is left unspecified, a minor gap given the tool's simplicity.

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 description coverage is 100% and the single parameter already documents '18 位统一社会信用代码'; the description merely repeats that constraint and adds no format rules, normalization behavior, or error semantics. Baseline 3 is appropriate when the schema does the work.

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 ('统一社会信用代码校验') with the exact input (18-digit code) and enumerates what is returned: GB 32100-2015 compliance, registration authority, administrative division code, and subject identifier code. An agent can tell this is a validation/parsing tool, distinct from siblings like cn-idcard or luhn-bank, without opening the 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 concrete downstream contexts ('企业主体核验、发票抬头校验、供应商准入的第一步') and a clear trigger condition ('模型算数不稳、法规口径易错时'). It does not name a sibling alternative or state when not to use it, so it stops short of full routing guidance, but the usage context 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.