Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

采购合同风险点检测

procurement-contract

采购合同风险点检测:采购/供货合同过一遍:预付款比例、验收标准、质保、逾期违约金、单方变更、知识产权、不可抗力、管辖。 检测维度:预付款过高、验收标准模糊、质保缺失、逾期违约金过低、单方变更、知识产权不清、不可抗力滥用、管辖不利。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景:Agent 处理合同/文案/协议/政策文本时,在交付给人之前做一道确定性合规体检。

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": {
      "text": "<text>"
    },
    "name": "procurement-contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes待检测的中文原文(合同条款、广告文案、协议、政策文本等整段贴入)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that whole Chinese text is passed in and that hit risk points, severity levels, and remediation suggestions are returned, plus that the check is deterministic, but it does not state whether the operation is read-only or how contract text is handled.

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 description is front-loaded with the purpose, then the reviewed clauses, detection dimensions, input/output, and applicable scenario. The two enumerated lists overlap somewhat, but they remain scannable and each part supports understanding the detector.

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 detector with no annotations and no output schema, the description adequately explains what is checked, what input is expected, what is returned, and when to use it. It still leaves operational details such as read-only behavior, data handling, and sibling routing implicit.

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?

There is one parameter with 100% schema description coverage; the schema already defines it as the Chinese source text with examples such as contract clauses, ad copy, agreements, and policy text. The description only restates that whole Chinese text should be passed in, adding no length, format, or other constraint beyond the schema.

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 states a specific verb and resource: risk-point detection on procurement/supply contracts, and enumerates the procurement clauses and risk dimensions it checks. It clearly distinguishes this domain from sibling contract tools such as labor-contract, loan-contract, and rental-contract.

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 concrete usage context: an Agent processing contracts, copy, agreements, or policy text should run it before delivering work to a human. It does not explicitly state when not to use it or name alternative sibling tools for other contract types.

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.