Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

竞业限制补偿计算器

noncompete-pay

竞业限制补偿计算器:按离职前月平均工资的 30% 算竞业限制月补偿,并校验是否低于当地最低工资;给出竞业期内补偿总额。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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>",
      "months": "<months>"
    },
    "name": "noncompete-pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYes竞业限制月数
localMinWageNo可选:当地最低工资标准
monthlySalaryYes离职前月平均工资(元)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the behavioral burden, and it does disclose the substantive algorithm (30% rule, minimum-wage validation, period total) and states that the output is deterministic and includes the underlying basis. It does not state whether the tool is a pure side-effect-free computation, nor what happens when the optional minimum wage is omitted or when the 30% falls below it — a gap, but the core behavior is well covered.

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?

Four short clauses, front-loaded with the calculation rule before the return behavior and usage scenario. The only waste is the leading repetition of the tool title, which restates the name.

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 stateless calculator with no annotations and no output schema, the description covers the formula, the validation step, the aggregate output, and the reason to prefer it over mental arithmetic — enough to invoke it correctly. It stops short of describing the returned fields or the handling of the optional minimum-wage input.

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; the description goes further by explaining the role of each value in the calculation — monthlySalary as the 30% base, localMinWage as the floor check, and months as the multiplier for the period total. That adds genuine operational meaning beyond the field labels.

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 names a specific verb-and-resource pair (compute noncompete monthly compensation, validate against local minimum wage, sum over the period) and states the actual rule applied — 30% of pre-departure average monthly salary. The domain is unambiguous versus sibling calculators such as overtime-pay and severance-pay, so an agent can route to it 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?

Explicit when-to-use guidance is given: call it when model arithmetic is unreliable or regulatory interpretation is error-prone, to obtain an exact answer. It gives clear context but names no exclusions and no alternative siblings for adjacent concepts (e.g. severance or overtime calculations), so the 'when not to use' half is left to inference.

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.