Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

工伤伤残待遇测算

gongshang-benefit

工伤伤残待遇测算:按伤残等级与本人工资,算一次性伤残补助金(1-10 级对应 27~7 个月)、能否按月领伤残津贴、劳动关系怎么处理,附《工伤保险条例》条号。省级的医疗/就业补助金不瞎填,明确告诉你需另查本省标准。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "level": "<level>",
      "monthlyWage": "<monthlyWage>"
    },
    "name": "gongshang-benefit"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes伤残等级 1-10
monthlyWageYes本人工资(元/月,受伤前 12 个月平均缴费工资)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden well: it declares the tool is deterministic, returns results plus 条例 article citations, and explicitly refuses to fabricate province-level subsidies, instead telling the caller to look up local standards. That disclosure of a deliberate scope limit is exactly the kind of behavioral context annotations would otherwise provide. Minor gaps remain around input validation for out-of-range levels and error behavior.

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, then outputs, then the provincial-subsidy caveat, then usage — a sensible priority order with no wasted clauses. The sentence '传入参数对象,返回确定性计算结果与依据' is largely restatement of the tool contract and could be trimmed.

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 two-parameter deterministic calculator with no output schema and no annotations, the description covers what is computed, what comes back (amount, monthly allowance eligibility, labor-relation guidance, statute references), and what is intentionally out of scope. An agent has enough to call it correctly; only edge-case behavior on invalid levels is 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 description coverage is 100%, and both parameters already carry their own definitions including the 12-month average contribution wage basis. The description only restates '按伤残等级与本人工资' and the 1-10 range, adding no semantics beyond the schema, so the baseline 3 applies.

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 (工伤伤残待遇测算) and enumerates the three concrete outputs: 一次性伤残补助金 with the 27~7 month scale, 伤残津贴 eligibility, and 劳动关系处理. It also bounds scope by excluding provincial 医疗/就业补助金, so an agent can tell it apart from severance-pay or overtime-pay siblings 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?

The line '适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案' gives an explicit triggering condition for using this tool rather than doing the math in-context. It stops short of naming sibling tools or stating when NOT to use it (e.g., non-work-injury severance), so it is clear context but not full alternates coverage.

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.