Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

设计合同条款清单

design-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": "design-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes你的立场

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does reasonably well: it states the response shape (必备要素、关键条款要点、对你不利的写法与谈判话术), that framing shifts with the chosen stance, and that this is neither a contract nor legal advice. It is silent on length/depth limits and on any versioning basis for the 《民法典》 承揽合同 skeleton, which keeps it from 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.

Conciseness4/5

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

The purpose and the four output components are front-loaded and each clause is doing work, but the opening pain-point riff (改稿无底洞 / 源文件 / 版权) is rhetorical setup rather than operational information an agent needs to select or call the tool.

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, no-output-schema generator, the description covers what is produced, how the parameter changes it, and its caveats — enough to call correctly. A note on output granularity or the legal-jurisdiction basis would close the last gap.

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% with a single self-explanatory enum, so the schema already does the work. The description mostly restates the parameter ("传入 { role } 指定你的立场") with only mild added meaning — that the whole checklist is reframed adversarially per stance.

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 deliverable — a clause checklist for design/creative contracts, scoped to the caller's stance — and grounds it in concrete design-industry risks (endless revisions, source files vs. final payment, copyright terms). That is far more specific than the sibling *-template tools' bare titles, though it never explicitly says how it differs from decoration-contract or labor-contract, leaving that inference to the agent.

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 conditions for invocation (pass { role } to pick 接单方 or 委托方) and a useful boundary: output is a checklist, not contract body text and not legal advice. It does not name an alternative tool for when a full drafted contract is actually wanted, so the when-not side is only partial.

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.

Resources