Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

经济补偿金计算器

severance-pay

经济补偿金计算器:按工作年限与月工资算 N / N+1 / 2N,自动处理"满半年算 1、不满半年算 0.5",附《劳动合同法》第四十七条依据与 3 倍社平上限提示。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "monthlySalary": "<monthlySalary>",
      "years": "<years>",
      "months": "<months>",
      "type": "<type>"
    },
    "name": "severance-pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesnormal / n+1 / 2n
yearsYes工作年限(整年)
monthsYes不满一年的月数
monthlySalaryYes离职前 12 个月平均月工资(元)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the key behaviors: the half-year rounding rule is applied automatically, the output is deterministic, and a legal citation accompanies the result. One ambiguity remains: the 3x social-average wage limit is only described as a 提示 (hint), so it is unclear whether the cap is applied to the figure or merely flagged.

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 compact and front-loads what is calculated before the rule details and the usage scenario. The sentence about passing a parameter object and returning a deterministic result is largely filler, which is the main reason it is not a 5.

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?

For a four-required-parameter calculator with no annotations and no output schema, the definition covers the computation logic well, but the return value is described only as a deterministic result plus legal basis, with no indication of the shape of the result (a single number or a breakdown) or whether the cap is applied. The agent can call it correctly, but it cannot predict the response precisely.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point by explaining how the months input is interpreted (full half-year counts as 1, less than half counts as 0.5) and by framing the type values as N / N+1 / 2N. That adds real meaning beyond the schema's bare 'normal / n+1 / 2n' string.

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 precise verb and resource: it computes severance pay in N / N+1 / 2N form from years of service and monthly salary. It also enumerates the exact rule set (half-year rounding, Article 47 basis, 3x social-average cap hint), so an agent can tell this is the severance calculator and not the overtime, noncompete, or other pay calculators in the catalog.

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 an explicit trigger condition: use this when the model's arithmetic is unreliable or the regulatory interpretation is error-prone, so the agent should prefer the tool over computing itself. It stops short of any when-not guidance or of naming a sibling alternative, 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.