Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

广告法违禁词检测

ad-law

广告法违禁词检测:电商 / 直播 / 朋友圈文案过一遍《广告法》:绝对化用语、虚假承诺、医疗功效、金融收益承诺、诱导性用语先挑出来。 检测维度:绝对化用语、虚假承诺、医疗功效宣称、金融收益承诺、诱导性用语、贬低竞品、虚构原价、广告未标识。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景: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": "ad-law"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work by declaring the check is deterministic (确定性合规体检) and stating what comes back — hit risk points, severity level and remediation advice — but says nothing about input length limits, whether results constitute legal advice, or how the eight dimensions are weighted, which matters for a compliance tool.

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-loads purpose, then dimensions, then output, then scenario — a sensible order with no filler sentences. Minor redundancy in that 绝对化用语 is listed twice (once in prose, once in the dimension list), costing a little tightness.

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 tool with no output schema, it covers purpose, input expectation, return contents and use context. What remains thin is operational detail — length limits and severity semantics — but nothing essential for correct invocation is missing.

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?

Only one parameter, and schema coverage is 100%, so the schema already documents it. The description's instruction to pass 传入整段中文原文 (the whole original Chinese text) reinforces rather than adds to the schema's 整段贴入 wording, so baseline 3 applies.

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?

Names a specific verb and resource — screening Chinese copy against 《广告法》 for prohibited wording — and enumerates the eight detection dimensions (绝对化用语、虚假承诺、医疗功效、金融收益承诺等), which lets an agent tell it apart from sibling contract/template tools 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 an explicit usage context: run it as a deterministic compliance check before delivering contract/copy/agreement/policy text to a human, and scopes inputs to 电商/直播/朋友圈 copy. It does not name exclusions or alternatives (e.g. non-Chinese text or purely numeric checks), so the routing guidance 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.