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

xiangguangyu-mcp-skills

by XYG-LUNA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

skill_cuilu

Forge AI skills with dual quality gate: fact-checking and depth analysis ensure reliable output from user inputs.

Instructions

[Cuilu] 淬炉——Skill锻造与双重质检引擎。边锻造边质检，每个Skill出厂前必须通过辩真事实核查与灼见深度穿透双重门禁。 (¥0.50/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_cuilu"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions process steps (forging while inspecting, two quality gates) and cost (¥0.50/call), which adds transparency. However, it lacks details on side effects, permissions, or reversibility.

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 concise with one sentence plus cost note. It front-loads the tool name and key idea. However, the metaphorical language adds ambiguity, slightly reducing clarity for a bilingual audience.

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 one parameter and no output schema, the description is adequate but incomplete. It explains what the tool does but not what the output looks like, how the dual inspection works in practice, or typical use cases. More context would help.

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?

With only one parameter 'query' and schema description coverage 100%, the schema already explains the parameter. The description adds no additional meaning beyond restating 'user input for this skill.'

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 clearly states it is a 'Skill forging and dual quality inspection engine' with specific verbs (forge, inspect) and resource (Skill). It distinguishes from sibling tools by mentioning dual gates (fact-checking and deep insight), but the metaphor '淬炉' may be unclear to some users.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description does not specify prerequisites, when not to use, or compare to sibling tools. The context of being a meta-skill for other skills is implied but not stated.

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