Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

定金押金合规判断

deposit-check

定金押金合规判断:判断定金是否超过合同总额 20%(超部分不产生定金效力,可主张返还),或押金比例是否偏高;说清"定金"与"押金/订金"的法律效力差别。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "totalAmount": "<totalAmount>",
      "depositAmount": "<depositAmount>",
      "type": "<type>"
    },
    "name": "deposit-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesdingjin(定金)或 yajin(押金/订金)
totalAmountYes合同总额(元)
depositAmountYes已付定金/押金(元)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden. It does disclose the core behavioral traits: it is a deterministic calculator that returns a result plus the legal basis, and it encodes the 20% statutory threshold and its consequence. It does not say what the output looks like, how '押金比例偏高' is thresholded, or how invalid or zero amounts are handled.

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?

The purpose and the rule are front-loaded, followed by the usage scenario, which is a sensible order. Some parenthetical legal asides and the closing '传入参数对象,返回确定性计算结果与依据' sentence add a little redundancy without breaking clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only behavioral source. It covers inputs and the general shape of the answer (result plus basis) but leaves the output structure, the 押金 'too high' threshold, and error/edge-case handling unspecified, which matters for a three-required-parameter legal calculator.

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 schema already documents all three parameters, setting a baseline of 3. The description adds meaning beyond that by tying the different legal tests to the `type` value (20% cap for 定金 versus a 'too high ratio' test for 押金/订金), which is genuinely useful for selecting the right enum value.

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 states a precise verb and resource: judge whether 定金 exceeds 20% of contract total (with the legal consequence that the excess has no deposit effect and can be reclaimed), or whether 押金 ratio is too high, plus explain the legal difference between 定金 and 押金/订金. That is a specific computational rule set, not a restatement of the title, and it is clearly distinct from the contract-drafting and other legal-check siblings.

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 when-to-use trigger: call it when the model's arithmetic is unreliable or the regulatory reading is error-prone, so the agent gets an accurate answer. It does not name a sibling alternative or state when NOT to use it, which keeps it short of a 5.

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.