中国社保与薪税计算器 (China Shebao & Payroll Tax MCP)

经济补偿金与裁员赔偿测算

calculate_severance_pay

Read-onlyIdempotent

测算经济补偿金（N、N+1、2N、N+2）、3倍社平和12年封顶及超额个税。必须分别提供适用年度的补偿社平月工资 avgWage 和当地税务公告免税额度 taxFreeLimit；不可用社保缴费上限代替。

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>",
      "avgWage": "<avgWage>",
      "taxFreeLimit": "<taxFreeLimit>"
    },
    "name": "calculate_severance_pay"
  }
}

Input Schema

Name	Required	Description
`city`	No	工作所在城市名称或代码，仅用于标注地区，不自动推算补偿社平工资或免税限额。
`type`	No	补偿方案类型：N（正常到期/提前30天通知）、N+1（常见无过失性辞退/裁员，含1个月代通知金，默认）、2N（违法解除赔偿金）、N+2（协商补充方案）。
`avgWage`	Yes	适用年度经济补偿的当地职工月平均工资（元/月，必填），请核对当地公告，不是养老缴费上限除以3。
`workYears`	No	工作年限（年，如 3 或 3.5 年，若输入 workMonths 则优先按 workMonths）。
`workMonths`	No	工作月数（总在职月数，如 40 个月；若未填写则按 workYears × 12 折算）。
`noticeSalary`	No	上个月实际工资（元，用于代通知金基数，可选；若未指定则默认等于 monthlySalary，代通知金依法不执行 3 倍社平封顶）。
`taxFreeLimit`	Yes	当地税务公告的一次性解除劳动关系补偿收入免税额度（元，必填），与补偿社平月工资分别核对。
`monthlySalary`	Yes	离职前12个月平均工资（元/月，全部应发工资，含绩效、奖金、津贴、加班费等）。

Output Schema

Name	Required	Description	Default
`tax`	Yes
`canonicalUrl`	Yes
`netSeverance`	Yes
`taxFreeLimit`	Yes
`grossSeverance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 8, 2026

changedInput schema / properties / avgWage / description

Previous value: -"当地职工月平均工资（元/月，可选；若指定则覆盖城市默认社平工资）。"New value: +"适用年度经济补偿的当地职工月平均工资（元/月，必填），请核对当地公告，不是养老缴费上限除以3。"

addedInput schema / properties / avgWage / exclusiveMinimum
```
Added value: +0
```

changedInput schema / properties / city / description

Previous value: -"工作所在城市名称（如\"北京\"、\"上海\"、\"深圳\"、\"广州\"、\"杭州\"等），自动带出该城市社平工资及 3 倍封顶与免税限额。"New value: +"工作所在城市名称或代码，仅用于标注地区，不自动推算补偿社平工资或免税限额。"

addedInput schema / properties / taxFreeLimit

Added value: +{
+  "description": "当地税务公告的一次性解除劳动关系补偿收入免税额度（元，必填），与补偿社平月工资分别核对。",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / workMonths / minimum
```
Added value: +0
```
changedInput schema / properties / workMonths / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / required

Previous value: -[
-  "monthlySalary"
-]New value: +[
+  "monthlySalary",
+  "avgWage",
+  "taxFreeLimit"
+]

AddedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive/closed-world, so the description focuses on domain behavior: which statutory caps apply (3x social average, 12-year limit), that tax applies to the excess portion, and that these rules interact with the two required local figures. The main warning against the common wrong input (contribution ceiling instead of social average) is real added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the calculation scope, then the mandatory-input constraint. No filler, no restatement of the title.

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?

With a rich schema, full description coverage, and an output schema, the description only needs to convey scope, caps, and the two required external figures, which it does. Minor gap: it does not clarify how workYears vs workMonths precedence interacts with the cap calculation beyond what the schema states.

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 baseline is 3. The description reinforces the two most error-prone required inputs (avgWage, taxFreeLimit), but that reinforcement largely duplicates what the schema descriptions already say, adding no new format or derivation detail.

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?

States a specific verb (测算) and precise resource scope: severance variants N/N+1/2N/N+2, the 3x social-average cap, the 12-year cap, and excess-portion tax. This scope is clearly distinct from the sibling calculators (income tax, take-home salary, pension), so an agent can route correctly without opening the schema.

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?

Gives a hard usage precondition: the applicable-year avgWage and the local tax-announced taxFreeLimit must both be supplied separately, and the social-insurance contribution ceiling must not be substituted. It does not name an alternative tool for cases outside severance (e.g. ordinary salary tax), so the when-not guidance is implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 中国社保与薪税计算器 (China Shebao & Payroll Tax MCP) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.