Skip to main content
Glama
Sign In
xiangguangyu-mcp-skills

xiangguangyu-mcp-skills

by XYG-LUNA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

skill_contract-guardian

Reviews contracts to identify risky clauses, extract critical information, and monitor expiration dates.

Instructions

[Contract Guardian] 合同卫士 — AI合同审查助手，识别风险条款、提取关键信息、追踪到期日 (¥0.10/call)

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": {
      "query": "<query>"
    },
    "name": "skill_contract-guardian"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes用户输入内容 / user input for this skill

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided. Description discloses core functions and cost per call, but lacks details on limitations (e.g., input format expectations, result structure, error handling) that could help an agent anticipate behavior.

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?

Description is concise with a single sentence listing key functions and pricing. No wasted words, but could benefit from structured sections for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should clarify return format. It lists functions but not how results are presented. Adequate for a simple skill, but lacking detail on the output.

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% with one parameter 'query' described as 'user input for this skill'. Description adds no extra meaning beyond the schema, so baseline score of 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?

Description clearly states the tool is an AI contract review assistant (合同审查助手) and lists specific functions: identify risk clauses, extract key info, track expiry dates. This distinguishes it from sibling skills which focus on other domains (e.g., ad-copywriter, game-audio).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: use for contract review. No explicit when-to-use or when-not-to-use guidance, and no comparison to sibling skills despite being in a list of specialized skills.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools