Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

装修合同条款清单

decoration-template

装修合同条款清单:装修是家庭纠纷最密集的场景:增项、以次充好、工期拖延、甲醛超标。按你的立场列出这份合同必须锁死的 9 项要素与 7 个关键条款,含付款节点比例与隐蔽工程验收。 传入 { 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": "decoration-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes你的立场

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does well on output shape (必备要素、关键条款要点、对你不利的写法与谈判话术) and on scope limits (清单非合同正文、不构成法律意见), but it never states what the response actually contains in bulk or what changes the stance produces beyond 对你不利 wording.

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?

Front-loaded with motivation (增项、以次充好、工期拖延、甲醛超标), then scope, then output, then disclaimer. The risk preamble is slightly promotional but short enough to earn the framing, and no sentence is redundant.

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?

For a single-parameter tool with no output schema and no annotations, the description covers input, output components, and legal caveat. At the same time, it doesn't say whether the 9 elements / 7 clauses are fixed universally or vary by role, and it doesn't state format length, leaving the agent to guess the expected output.

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?

With 1 parameter and 100% schema coverage (enum 业主 / 装修方 already labeled 你的立场), the schema does the heavy lifting. The description only adds that role shifts the perspective to your disadvantage clauses and negotiation talking points, which is a small increment over the enum label.

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 states a concrete verb and resource: 列出装修合同必须锁死的 9 项要素与 7 个关键条款, filtered by stance. The line 输出为清单不是合同正文 implicitly separates it from a contract-drafting sibling such as decoration-contract, but no sibling is named, so differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context (pre-signing renovation contract, per-stance view) is implied by 按你的立场列出 and by the enumerated risks, and the caveat 输出为清单不是合同正文 sets a negative boundary. However, it never says explicitly when to pick this over decoration-contract or zhuangxiu-budget, so routing is left to inference.

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.