Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

劳动合同条款清单

labor-template

劳动合同条款清单:不给你一份"通用合同"——按你的立场逐条告诉你:这份劳动合同必须写哪几项、每一栏填错会怎样、哪句话对你不利、谈判时怎么接。骨架依《劳动合同法》第十七条九项必备条款。 传入 { role } 指定你的立场,返回必备要素、关键条款要点、对你不利的写法与谈判话术。注意:输出为清单不是合同正文,不构成法律意见。

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": {
      "role": "<role>"
    },
    "name": "labor-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes你的立场

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 disclose what the output contains (mandatory elements, key clause points, unfavorable wordings, negotiation scripts), the statutory skeleton, and the scope limit. It does not disclose whether the output is legally binding, length, or whether the same role always yields the same checklist, so behavioral coverage is decent but incomplete.

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?

It is front-loaded with the core distinction and then lists what is returned. The opening rhetorical flourish ('不给你一份"通用合同"') is slightly promotional but earns its place by defining the contrast, and the trailing disclaimers are compact.

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, no-output-schema tool, the description covers what the output is, what it is based on, and what it is not. The only gap is the exact structure of the returned checklist, which would help an agent format downstream use, but the summary is reasonably sufficient.

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?

Only one parameter, whose enum is fully documented in the schema. The description adds meaning by explaining that role selects the *stance* from which the checklist, risk warnings, and negotiation scripts are written — a real semantic addition beyond '你的立场'.

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?

The description states a specific resource (劳动合同条款清单) and makes explicit what it is not — not a generic contract draft, but a per-clause checklist grounded in Article 17 of the Labor Contract Law. It implicitly separates itself from contract-generation siblings such as labor-contract, though it never names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context ('pass { role } to specify your stance') and a boundary (output is a checklist, not contract text, and not legal advice). However, it never says when to pick this over the sibling labor-contract or the other *-template tools, so the agent must infer.

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.