Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

隐私政策合规检测

privacy-policy

隐私政策合规检测:App / 小程序隐私政策过一遍《个人信息保护法》:告知同意、超范围收集、默认勾选、第三方共享、删除注销、未成年人、跨境。 检测维度:未告知目的、超范围收集、默认勾选同意、第三方共享未告知、删除注销权缺失、未成年人保护缺失、跨境传输未告知、联系方式缺失。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景:Agent 处理合同/文案/协议/政策文本时,在交付给人之前做一道确定性合规体检。

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": {
      "text": "<text>"
    },
    "name": "privacy-policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes待检测的中文原文(合同条款、广告文案、协议、政策文本等整段贴入)

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?

With no annotations at all, the description carries the full burden and mostly meets it: it states that the entire Chinese original text is passed in, that the check is '确定性' (deterministic, not probabilistic), and that the output is risk points plus severity plus remediation advice. What is missing is any disclosure of input-length limits, whether results are advisory vs legal opinion, or failure/edge behavior.

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?

The structure is front-loaded and logical: capability, then detection dimensions, then I/O, then the scenario. The one inefficiency is that the first sentence already lists the legal topics that the subsequent '检测维度' list re-enumerates in more granular form, creating mild redundancy in an otherwise dense, low-waste description.

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, annotation-free tool with no output schema, the description is close to sufficient: input expectations, output content, detection dimensions, and use case are all present. It falls short only on output shape specifics and input size limits, which an agent might need to call it reliably at scale.

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 coverage is 100% for the single 'text' parameter, so the schema already documents it; the description reinforces the semantics by stressing '传入整段中文原文' (pass the whole passage, not snippets), which is meaningful usage guidance beyond the field label. It does not add format or size constraints, so it stays just above baseline.

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 gives a specific verb and resource (privacy policy compliance check against PIPL for App / mini-program) and enumerates the eight detection dimensions, so an agent can immediately tell this is a privacy-policy audit rather than a general contract review. It also names what it returns (hit risk points, severity, remediation suggestions), which further separates it from siblings like labor-contract or ad-law.

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?

The final sentence provides a clear when-to-use context: run a deterministic compliance check before delivering contract/copy/agreement/policy text to a human. That is actionable guidance rather than an implied use. However, it does not explicitly exclude or route to the many adjacent sibling tools (ad-law, contract tools), and the schema's broad '合同条款、广告文案' phrasing slightly blurs the intended scope.

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.