Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

试用期合规计算

probation-check

试用期合规计算:按合同期限判断试用期上限(不满 3 个月不得约定 / 1 个月 / 2 个月 / 6 个月),并校验试用期工资是否低于约定工资的 80%。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "contractMonths": "<contractMonths>",
      "probationMonths": "<probationMonths>",
      "monthlySalary": "<monthlySalary>",
      "probationSalary": "<probationSalary>"
    },
    "name": "probation-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthlySalaryYes约定工资(元/月)
contractMonthsYes合同期限(月)
probationMonthsYes约定试用期(月)
probationSalaryYes试用期工资(元/月)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the important traits: this is a pure deterministic computation ('返回确定性计算结果与依据') with no side effects implied. What it omits is how violations are surfaced — whether the return flags an illegal probation length, an underpaid probation salary, or both — and any error behavior for invalid inputs.

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?

Three sentences, front-loaded with the actual rule logic, then input/output shape, then the usage trigger. No sentence is redundant and the compressed parenthetical tier list stays readable.

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 convey the return, and it does ('返回确定性计算结果与依据'). For a four-required-parameter deterministic calculator this is nearly sufficient; the remaining gap is the exact shape of the result and the handling of boundary or conflicting inputs.

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 baseline would be 3, but the description adds real semantics: it explains that contractMonths drives the cap tier and that probationSalary is compared against 80% of monthlySalary. That tells the agent how the four numbers relate to each other, not just what they are.

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 the exact computation: mapping contractMonths to the statutory probation cap tiers (<3 months = none, 1/2/6 months) and checking probationSalary against 80% of monthlySalary. That level of rule specificity makes it immediately distinguishable from sibling calculators such as severance-pay or overtime-pay, which compute different quantities.

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 for use: '适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案' — i.e., call this instead of reasoning about the rule yourself. It does not state exclusions or name a sibling tool for adjacent questions, but the 'when' condition is clear and actionable.

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.