Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

服务外包合同风险点检测

outsourcing-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": "outsourcing-contract"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose what matters: the check is deterministic ('确定性合规体检'), and it returns hit risk points, a severity level, and remediation suggestions. It omits limitations such as input length limits or that the result is advisory rather than legal advice, which is a meaningful gap for a screening tool, but the core behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is front-loaded and well ordered (purpose, then dimensions, then input/output, then scenario). However, the eight risk dimensions are listed twice in almost identical wording ('范围无边界、验收主观…' then again after '检测维度:'), and that duplication wastes space without adding information.

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 one-parameter tool with no output schema, the description supplies what an agent needs: the trigger scenario, the input form, and a summary of the return payload (hit points, level, remediation). Nothing essential to invoking it correctly is missing, though edge conditions such as text length limits are unaddressed.

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?

The single parameter is fully documented in the schema (100% coverage), which already says to paste a whole block of Chinese text of contract clauses, ad copy, agreements, or policies. The description only restates '传入整段中文原文', reinforcing the whole-block requirement but adding no new syntax or formatting guidance, so this is baseline 3.

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: '服务外包合同风险点检测' (outsourcing-contract risk detection), and enumerates the eight specific risk dimensions it checks. The domain in the tool name and description clearly sets it apart from labor-contract, loan-contract, and rental-contract, but the definition itself never distinguishes this tool from those siblings.

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 window — '接/发发外包前过一遍' and '在合同…交付给人之前' as a pre-handoff check. It does not state when an alternative should be used (for example, 'for NDA text, use nda') or any exclusions, so it falls short of explicit routing.

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.