Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

劳动仲裁时效测算

limitation-clock

劳动仲裁时效测算:输入「知道权利被侵害之日」或「离职之日」,算出仲裁时效截止日与剩余天数。工资/加班费争议在劳动关系存续期间不受一年限制,这一条很多人不知道,工具会按你的情形自动判定。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "knowDate": "<knowDate>",
      "type": "<type>"
    },
    "name": "limitation-clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYeswage(劳动报酬)或 other(其他争议)
knowDateYes知道或应当知道权利被侵害之日 YYYY-MM-DD
relationEndDateNo可选:劳动关系终止日 YYYY-MM-DD

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?

No annotations are supplied, so the description carries the full burden. It discloses the key behavioral rule that wage and overtime disputes during an ongoing employment relationship fall outside the one-year limit and are judged automatically, and it says the output is a deterministic result with its legal basis. It does not describe behavior for edge cases, such as when relationEndDate is omitted or when the rules conflict.

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 short and leads with the purpose and formula logic; the usage trigger comes last in the right place. The sentence '这一条很多人不知道' is rhetorical padding, and '传入参数对象' restates the obvious. These are minor wastes in an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should describe the shape of the response and any edge cases. It says only that the result is 'deterministic ... 与依据' and never explains what the basis field contains or what happens when relationEndDate is missing. For a simple three-parameter calculator, it is adequate but leaves the agent guessing about the output.

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 description coverage is 100%, so the schema already documents all three parameters, and the baseline is 3. The description echoes the keyword semantics of knowDate ('知道权利被侵害之日' or resignation date) but adds no new detail, such as how relationEndDate interacts with the wage/other branch. It neither adds meaning beyond the schema nor compensates for any gap.

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 opens with a concrete verb-plus-resource: it takes the date the right was infringed or the resignation date and computes the arbitration limitation deadline and the remaining days. The purpose is unmistakable, and the tool is clearly distinct from pay-calculation siblings like overtime-pay or severance-pay. It never explicitly contrasts itself with any sibling, so it falls short of a 5.

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?

The description gives a clear condition for use ('适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案'), telling the agent to route here instead of doing date arithmetic or legal interpretation on its own. However, it states no exclusions: it does not say what types of disputes are out of scope, nor does it name any alternative tool. The guidance is solid but one-sided.

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.