Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

合伙协议条款清单

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

Input Schema

NameRequiredDescriptionDefault
roleYes你的立场

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 declares the output form (a checklist rather than contract text), the legal basis (民法典 第三编第二十七章, 967-977), and enumerates the four returned sections (必备要素、关键条款要点、不利写法、谈判话术). It also discloses the liability boundary ('不构成法律意见'). What is left unstated—whether output is exhaustive per stance or how long it runs—is minor for a read-only advisory generator.

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 content is front-loaded: what the tool is, how to call it, what comes back, and the disclaimer. The opening scenario sentence is the weakest element—it is persuasive framing rather than operational detail—but it still conveys the target use case. Remaining sentences (legal basis, output form, disclaimer) each contribute information the agent or user needs.

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, and the description describes the returned components explicitly, so nothing is missing on the return side. The tool is a read-only content generator with a single enum parameter that the description explains, and the caveats an agent or user needs (list not contract, not legal advice) are present. Nothing material for correct invocation is absent.

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?

Schema coverage is 100% and there is a single enum parameter, so the schema already defines both accepted values. The description nonetheless adds meaning by explaining the consequence of the parameter: the checklist is tailored to '你的立场', including clauses unfavorable to that stance and negotiation talking points, which tells the agent why the choice matters beyond '你的立场'.

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 specific resource and scope: a clause checklist for partnership agreements (出资、利润分配、亏损承担、决策权、退出), grounded in 民法典 967-977. It distinguishes itself from the contract-drafting siblings by stating '输出为清单不是合同正文', so an agent can tell it apart from labor-contract/rental-contract style tools. The opening narrative ('三四线开店…翻脸') frames the domain rather than naming an explicit verb-resource pairing, which keeps it just short of a 5.

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 a clear usage context (two acquaintances forming a store partnership) and instructs the agent to pass { role } to select the stance, which determines the returned content. It also sets expectations with two explicit boundary conditions: the output is a checklist, not contract text, and it is not legal advice. No explicit 'use X instead' routing to a sibling is provided.

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