Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

保密协议(NDA)风险点检测

nda

保密协议(NDA)风险点检测:签 NDA 前过一遍:保密范围、期限、违约金、单向义务、竞业混入、例外条款、返还销毁、管辖。 检测维度:保密范围无限、期限过长、违约金畸高、单向义务、竞业混入、缺例外条款、返还销毁不明、管辖不利。传入整段中文原文,返回命中风险点、等级与整改建议。适用场景: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": "nda"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the input convention (pass the entire Chinese original text), the output shape (hit risk points, severity level, remediation suggestions), and frames the check as deterministic. It does not state limitations such as language restriction beyond Chinese or behavior on non-NDA text.

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?

Front-loaded with purpose, but the risk list appears twice in near-identical form (once as the pre-sign checklist, once as 检测维度), which is redundant. Still readable and reasonably scoped.

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 tool, the definition covers input convention, output contents, and usage context adequately. The main gap is that output structure (fields or format of risk points and severity levels) is described only prose-wise.

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% and the single 'text' parameter is already documented as the full Chinese source text pasted in. The description's '传入整段中文原文' largely restates the schema, adding little new meaning; baseline 3 applies.

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?

States a specific verb and resource (NDA risk-point detection) and enumerates the concrete detection dimensions (unlimited confidentiality scope, excessive term, disproportionate penalty, one-way obligations, non-compete mixing, missing exceptions, unclear return/destruction, unfavorable jurisdiction). This makes it clearly distinguishable from document-specific siblings like labor-contract or privacy-policy.

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?

Gives a clear trigger ('sign NDA, run it first') and a usage context ('when an Agent handles contract/copy/agreement/policy text, before delivering to a human'). It does not explicitly say when to prefer a sibling tool (e.g., privacy-policy, labor-contract) for other document types, so it stops short of full routing guidance.

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.