Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

离职协议/协商解除风险点检测

separation-agreement

离职协议/协商解除风险点检测:签离职协议前过一遍:放弃全部权利、补偿低于法定、竞业无补偿、社保放弃、年终奖、永久保密、格式确认、单向违约。 检测维度:放弃全部权利、补偿低于法定、竞业无补偿、社保补缴放弃、年终奖剥夺、永久保密、格式确认不实、违约条款单向。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景: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": "separation-agreement"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does reasonably well: it discloses the output shape (命中风险点、等级与整改建议) and frames the check as deterministic (确定性合规体检), which tells the agent results are rule-based rather than generative. It omits any note on limits — language coverage (Chinese only), input length, or what happens for text outside the labor domain despite the mention of 文案/政策文本.

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 eight risk dimensions are listed twice in near-identical form (once as a pre-signing checklist, once as '检测维度:...'), which is redundant padding. Front-loading is otherwise good, with purpose, dimensions, return values and use case in a sensible order.

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 one-parameter tool with no output schema, the description covers input form, the eight checked dimensions, and the shape of the result (hits, severity, remediation advice), which is what an agent needs to call it. Remaining gaps are edge-case scope notes rather than blockers.

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% for the single `text` parameter, so the baseline is 3. The description reinforces that the whole passage must be pasted in ('传入整段中文原文'), but that largely repeats the schema's own '整段贴入' wording rather than adding new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource (离职协议/协商解除风险点检测) and enumerates eight specific detection dimensions, so an agent knows exactly what class of defect is checked. It stops short of naming a contrasting sibling (e.g., separation-template, severance-pay), so differentiation from tools with similar names must be inferred from the name rather than the text.

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?

'签离职协议前过一遍' and the 适用场景 sentence give a clear trigger point: run this before delivering contract/policy text to a human. There is no explicit when-not guidance and no named alternative tool to route away to, which keeps it below 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.