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

xiangguangyu-mcp-skills

by XYG-LUNA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

skill_bianzhen

Validates user input through adversarial testing across multiple AI models, comparing responses to detect inconsistencies and improve accuracy.

Instructions

[Bianzhen] 多模型对抗验证助手（跨平台版） (¥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_bianzhen"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

D1.5/5.0
Behavior1/5

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

No annotations exist and the description fails to disclose any behavioral traits such as read-only, destructive actions, authentication needs, or rate limits.

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

Conciseness2/5

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

Extremely short (one line) but lacks any structure or substantive content. Under-specification rather than efficient conciseness.

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

Completeness1/5

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

Description is incomplete for a tool with no output schema, no annotations, and only one parameter. It fails to explain what the tool does, returns, or how to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter 'query' with a generic description 'user input for this skill'. Schema coverage is 100% but the description adds no additional meaning beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a translated title 'Multi-model adversarial verification assistant (cross-platform version)' but lacks a verb and clear resource. It does not state what action the tool performs, only a domain hint.

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

Usage Guidelines1/5

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

No guidance on when or why to use this tool versus sibling tools like 'skill_cuilu' or 'skill_ad-copywriter'. No usage context provided.

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