Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

加班费计算器

overtime-pay

加班费计算器:按月工资与各类加班小时数,算出工作日 150%、休息日 200%、法定节假日 300% 分别该拿多少,附《劳动法》第四十四条依据与计算公式。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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>",
      "workdayHours": "<workdayHours>",
      "restdayHours": "<restdayHours>",
      "holidayHours": "<holidayHours>"
    },
    "name": "overtime-pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
holidayHoursYes法定节假日加班小时
restdayHoursYes休息日加班小时
workdayHoursYes工作日加班小时
monthlySalaryYes月工资(元)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/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 does disclose the payoff: deterministic results plus the Article 44 legal basis and formula, which is meaningful for a calculation tool. It stops short of the mechanics an agent might want — the monthly-to-daily divisor convention, rounding, and how zero-hour inputs are handled — so gaps remain.

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 purpose and rate structure, then the contract with the caller. Mostly tight; '传入参数对象' is filler that restates the schema's top-level type and could be cut without loss.

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?

There is no output schema, so the description must cover returns, and it does so briefly with '返回确定性计算结果与依据'. For a four-required-parameter, single-purpose calculator, that is nearly enough; only the divisor and rounding convention are left unstated.

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 all four parameters are documented there, so the baseline is 3. The description adds useful mapping context by tying hour types to their respective 150%/200%/300% multipliers, but no unit, default, or validation nuance beyond the schema.

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 resource (计算加班费), names all four rate tiers (工作日 150%、休息日 200%、法定节假日 300%) and the inputs that drive them. Among sibling pay calculators such as severance-pay and noncompete-pay, the subject matter alone makes this one unmistakable.

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?

The '适用场景' line gives a trigger condition — model arithmetic is unreliable or the legal standard is easy to get wrong — which is real but generic justification rather than task selection guidance. No when-not conditions and no named alternatives, though the sibling set is domain-distinct enough that little routing guidance is needed.

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.