Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

离职协议条款清单

separation-template

离职协议条款清单:离职协议签错,等于白送一笔钱或白丢一笔钱。按你的立场列出必须写清的 9 项:补偿怎么算、年假怎么折、竞业到底启不启动、那句"双方再无争议"到底放弃了什么。 传入 { 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": "separation-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes你的立场

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and does reasonably well: it discloses what is returned (必备要素、关键条款要点、对你不利的写法、谈判话术), that output is a checklist rather than contract prose, and that it is not legal advice. Missing are any note on statelessness, jurisdiction assumptions, or whether content is static template text.

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-loaded with the risk hook, then the deliverable, then the input, then the return contents and caveats. The opening rhetorical flourish costs a few words but earns them by signaling the tool's purpose; the rest is dense and waste-free.

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, no-output-schema tool, the description covers input, output shape, and the key limitation (checklist, not legal advice). A short note on the fixed 9-item structure's basis or jurisdiction would close the remaining gap.

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% and the single enum parameter already documents 你的立场 with values 员工/公司. The description adds only that the stance drives which wording is flagged as unfavorable and which negotiation scripts are produced — useful framing, but modest beyond the schema.

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 specific verb and deliverable: list the 9 items that must be spelled out in a separation agreement, per stance. It also separates itself from contract-drafting siblings by declaring '输出为清单不是合同正文', so an agent knows this is a checklist generator, not an agreement writer. It stops short of naming a specific sibling 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?

Usage is implied by the pain-point framing ('离职协议签错,等于白送一笔钱或白丢一笔钱') and by the explicit instruction to pass { role } to set your side. The 'not contract text, not legal advice' line sets a boundary on expectations, but there is no explicit when-to-use versus when-to-use-a-sibling guidance.

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.