Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

租房合同风险点检测

rental-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": "rental-contract"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description has to be self-sufficient and it mostly is: it discloses the legal basis (《民法典》租赁合同章), that the tool is deterministic ('确定性合规体检'), that the input must be the entire Chinese source text, and that the output is 命中风险点、等级与整改建议. What it omits is any caveat — that results are not legal advice, that non-rental text yields little, or whether input text leaves the environment. It adds real behavioral value but not the complete picture a no-annotation tool ideally carries.

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 opening sentence is well front-loaded and the return-value sentence is placed well, but the risk list is effectively given twice: 违约金/维修责任/提前收房/二房东/自动续租 appear in the first sentence and again in the 检测维度 list, differing only in wording. Trimming the first enumeration would make it tighter. The content is dense but not wasteful enough to drop below 3.

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 one-parameter tool with no output schema, the description covers what an agent needs: the input form (whole Chinese text), the output shape (hit risks, severity level, remediation advice), and the intended workflow position. The one wobble is scope — a rental-contract checker declared applicable to 广告文案/政策文本 — which could confuse an agent about how far the tool generalizes.

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 coverage is 100% and the single parameter is already documented as '待检测的中文原文…整段贴入'. The description restates '传入整段中文原文', reinforcing the whole-passage requirement rather than shortening, but adds no new format, length, or encoding guidance beyond the schema. Baseline 3 for a fully documented single parameter is appropriate.

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 names a specific verb and resource — detecting risk points in a Chinese rental contract — and enumerates the exact risk categories checked (押金不退、违约金过高、维修责任转嫁、提前收房、水电乱收费、二房东风险、自动续租、定金不退). An agent can immediately tell this is an analysis/checking tool rather than a template generator. It stops short of 5 because it never names a sibling such as rental-template to make the boundary explicit, leaving the agent to infer the distinction.

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 states a clear usage context: when an agent processes contract/copy/agreement/policy text, run this before delivering to a human as a deterministic compliance check. That gives an agent a concrete trigger. There are no explicit exclusions or named alternatives (e.g., when to use rental-template or deposit-check instead), so it falls short of 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.