Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

劳动合同风险点检测

labor-contract

劳动合同风险点检测:入职签合同前过一遍《劳动合同法》:试用期、竞业限制、违约金、社保、工时、单方调岗等高风险条款。 检测维度:试用期超限、竞业限制无补偿、违约金滥用、社保缺失、工时违法、单方调岗、放弃权利条款、解除条件不对等。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景: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": "labor-contract"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses deterministic compliance checking plus the return of hit risk points, severity levels, and remediation suggestions. It does not state legal-advice limitations, input size limits, or explicit read-only/no-side-effect status.

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 description is front-loaded with the purpose, then moves through detection dimensions, input/output, and applicable scenario. It lightly repeats the title and parameter guidance, but no major section is wasted.

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 analysis tool without an output schema, the description explains what is returned: hit risk points, severity, and remediation suggestions, and it frames the pre-delivery compliance-check scenario. It leaves exact output shape and input limits unspecified, but is sufficient for this tool's complexity.

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?

There is one required text parameter with 100% schema description coverage, and the schema already explains that full Chinese original text should be pasted in. The description adds only '传入整段中文原文', which is largely redundant with the schema, so the 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?

The description states a specific verb and resource: risk-point detection for labor contracts, with enumerated high-risk clauses such as probation, non-compete, liquidated damages, social insurance, working hours, and unilateral transfer. It is distinguishable from template-generation and single-check sibling tools by its full-contract compliance review scope, even without naming a sibling explicitly.

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?

It gives clear usage context: before signing an employment contract and before delivering contract/copy/agreement/policy text to a human. It does not state when-not conditions or name alternatives, so the agent must infer boundaries from the scenario.

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.