Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

税前应发→到手速算

salary-net

税前应发→到手速算:拿到offer想知道实际到手多少?按税前月薪、五险一金个人比例、专项附加扣除,速算大致到手工资,方便比较offer。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "gross": "<gross>",
      "socialRate": "<socialRate>",
      "special": "<special>"
    },
    "name": "salary-net"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYes税前月薪(元)
specialYes专项附加扣除月额(可选)
socialRateYes五险一金个人比例(可选,默认0.105)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 disclosure burden. It does disclose two useful traits: the output is a deterministic computed result plus its basis, and the figure is explicitly approximate (大致到手工资), which sets expectations. It does not state the tax assumptions or rounding/precision behaviour, which matters for a statutory calculation tool with zero annotation coverage.

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

Conciseness3/5

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

The core operation is front-loaded, but the offer-comparison rhetorical question and '方便比较offer' repeat the same motivation, and the title is effectively restated. It is not bloated, yet several clauses could be merged without losing information.

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 three-parameter calculator with full schema coverage and no output schema, the description supplies purpose, the approximate nature of the result, what the return contains, and a usage trigger. The remaining gap is that it never says which regulatory baseline or tax brackets the deterministic result follows, which an agent comparing offers might want.

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 three parameters and the default of 0.105 are already documented structurally. The description restates the inputs (gross salary, personal social-insurance rate, special deductions) without adding unit conventions, valid ranges, or what the 'basis' output contains. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific transformation: gross monthly salary plus social-insurance personal rate plus special deductions yields approximate take-home pay, framed around comparing offers. That is a clear verb+resource statement an agent can act on. It does not explicitly distinguish itself from salary-adjacent siblings such as overtime-pay or noncompete-pay, which keeps it at 4 rather than 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?

It gives an explicit trigger condition: call this when the model's arithmetic is unreliable or regulatory interpretation is error-prone, to get an accurate answer. That is clear context for when to invoke it. It names no exclusions and no alternative tools for adjacent salary questions, so it falls short of the 5 bar.

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.

Resources