Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

借条/借款条款清单

loan-template

借条/借款条款清单:按你的立场列出借条必须写清的 9 项要素,以及"转账备注写什么、利率上限多少、要不要写保证人、诉讼时效怎么算"。借钱给熟人最怕的不是不还,是没证据。 传入 { 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": "loan-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?

No annotations are supplied, so the description carries the full load, and it does disclose the important traits: output is a checklist rather than a contract, it is not legal advice, and the return includes required elements, key clause points, wording unfavorable to the user's side, and negotiation talking points. The main remaining gap is that nothing is said about output length or format, but for a non-destructive reference tool the behavioral profile is well covered.

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, the scoping examples, the role parameter, and the disclaimer are all front-loaded and each does work. The motivational line about lending to acquaintances is the only soft sentence, though it does establish the use case; overall it is dense without being padded.

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?

With a single required enum parameter, no output schema, and no annotations, the description supplies enough: what the checklist contains, how role changes the output, and the disclaimer. An agent could invoke this correctly on the first try; only the response's shape and size are left unspecified, which is minor here.

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 already 100% and the enum is self-explanatory, yet the description still adds meaning: { role } sets the user's stance and determines which clauses are flagged as unfavorable to them, which is more than the schema's '你的立场' conveys. That perspective-shifting effect is the key thing an agent needs to know when choosing a role value.

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 specific verb and resource: it lists the 9 elements an IOU must contain, plus four concrete sub-questions (transfer memo wording, interest-rate cap, guarantor, statute of limitations). It also explicitly separates itself from the contract-writing sibling by stating '输出为清单不是合同正文' (output is a checklist, not contract body text), so an agent can pick between this and loan-contract without opening 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?

Usage context is clear: this is for lending to acquaintances where the risk is lack of evidence, and the 'not contract body text / not legal advice' notes tell the agent when this tool is insufficient. It does not name loan-contract as the alternative for full contract drafting, leaving that routing to inference, which keeps it short of a 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.