xiangguangyu-mcp-skills

skill_game-audio

Design game audio assets including sound effects, music, and ambient sound. Describe your needs to generate custom audio solutions and production resources.

Instructions

[Game Audio] 游戏音频设计——音效/配乐/环境音方案与资源制作 (¥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_game-audio"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	用户输入内容 / user input for this skill

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Jul 14, 2026

TDQS

C2.6/5.0

Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the domain and cost, without explaining what happens when called (e.g., generates text, returns audio files), required permissions, or side effects. This is critically insufficient for an agent to predict outcomes.

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 a single, dense line in Chinese and English, conveying topic and cost efficiently. It is front-loaded with the key identifier '[Game Audio]'. However, a slightly more structured presentation (e.g., separating purpose from cost) could improve clarity.

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?

For a creative skill with no output schema, the description should explain what the tool produces (text? audio files? design plans?) and how to interact with it. It provides none of this context, leaving the agent without enough information to use it effectively.

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 schema covers 100% of parameters (one 'query' field). The description adds no additional meaning beyond the schema's 'user input for this skill'; it does not specify expected format, language, or examples. Baseline 3 applies since schema coverage is high, but the description adds no value.

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 indicates it is a skill for game audio design, including sound effects, music, and ambient sounds. It specifies the domain and type of output, distinguishing it from sibling tools. However, it lacks an explicit verb specifying the tool's action (e.g., 'generates' or 'creates'), so it is not a perfect 5.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, limitations, or context for invocation. The only extra information is the cost per call, which does not help an agent decide when to select this tool.

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

Deploy Server