Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

租房合同条款清单

rental-template

租房合同条款清单:按你的立场逐条列出这份租约必须写清的事项:押金怎么退、维修谁负责、能不能提前收房、水电能不能加价、二房东怎么防。骨架依《民法典》第七百零四条。 传入 { role } 指定你的立场,返回必备要素、关键条款要点、对你不利的写法与谈判话术。注意:输出为清单不是合同正文,不构成法律意见。

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": {
      "role": "<role>"
    },
    "name": "rental-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes你的立场

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?

With no annotations provided, the description carries the full burden, and it does disclose the key traits: the return content (必备要素、关键条款要点、对你不利的写法与谈判话术), the sourcing basis (《民法典》第七百零四条), and two important limits—it is a checklist rather than contract text and does not constitute legal advice. It does not describe depth, length, or variation between the two roles' outputs, which keeps it shy of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and topic list lead, the parameter instruction and return description follow, and the caveats close. Every clause contributes: the topic list makes the scope concrete, and the disclaimer prevents misuse. There is no filler.

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

Completeness5/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 shape—it does so explicitly (必备要素、关键条款要点、不利写法、谈判话术). For a single-enum-parameter generation tool, the addition of the legal basis and the not-legal-advice caveat covers everything an agent needs before invoking it.

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 enum already documents the two stances (承租人/出租人) with a description of 你的立场. The description restates this as 指定你的立场 and implies the output is perspective-dependent, but adds no new detail such as how the two roles' checklists diverge.

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 uses a concrete verb and resource (逐条列出这份租约必须写清的事项) and enumerates the specific topics covered: 押金退还、维修责任、提前收房、水电加价、二房东风险. It also distinguishes the output from a full contract (输出为清单不是合同正文), which separates it from the sibling rental-contract tool without needing either 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?

It gives clear context for the parameters: 传入 { role } 指定你的立场, and states what each stance returns. The line 输出为清单不是合同正文 implicitly tells the agent when this is preferable to generating a contract, but it never explicitly names rental-contract or states exclusion conditions, so it falls short of a full when/when-not rubric.

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.