Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

借款/民间借贷风险点检测

loan-contract

借款/民间借贷风险点检测:出借前过一遍:砍头息、利率超限、复利、担保缺失、空白合同、暴力催收、提前还款罚息、管辖。 检测维度:砍头息、利率超限、复利计息、担保缺失、空白合同、暴力催收条款、提前还款罚息、管辖不利。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景:Agent 处理合同/文案/协议/政策文本时,在交付给人之前做一道确定性合规体检。

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": {
      "text": "<text>"
    },
    "name": "loan-contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes待检测的中文原文(合同条款、广告文案、协议、政策文本等整段贴入)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does reasonably well: it discloses that the check is deterministic (确定性), whole-text, and returns hit risk points, severity levels, and remediation suggestions — effectively describing output behavior despite no output schema. It omits caveats such as whether results are legal advice or whether any risk categories are unsupported, which keeps it below a 5.

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 intent and usage trigger are front-loaded and easy to scan, but the eight risk dimensions are enumerated twice — once in the opening list and again in "检测维度" — with identical items (砍头息, 利率超限/利率超限, 担保缺失, 空白合同, 暴力催收, 提前还款罚息, 管辖). That duplication is pure waste in an otherwise short description.

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 single-parameter, non-destructive text-analysis tool with no output schema, the description covers input form, checked dimensions, and the shape of the return (hits, levels, suggestions). Nothing critical to correct invocation is missing, though a note on scope limits (e.g. Chinese text only, not legal advice) would round it out.

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?

Only one parameter with 100% schema description coverage, so the schema already defines it fully; the description adds the useful operational note "传入整段中文原文" (paste the whole passage, not excerpts), which meaningfully constrains input form beyond the schema wording.

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+resource (借款/民间借贷风险点检测) and enumerates the eight concrete risk dimensions it checks, so an agent knows exactly what class of output to expect. It is clearly distinguishable from template-generation siblings such as loan-template by the word 检测 and the pre-delivery check framing.

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?

"出借前过一遍" and "在交付给人之前做一道确定性合规体检" give clear situational triggers, and the 适用场景 line enumerates contract/copy/agreement/policy text. It stops short of naming when NOT to use it or pointing at a sibling tool (e.g. loan-template) for drafting, so it is clear context without explicit exclusions.

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.