Skip to main content
Glama
Sign In
netease-music-mcp

netease-music-mcp

by xinyu68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

netease_stop

Stops audio playback immediately, resets progress, and keeps the current queue while canceling any pending song requests.

Instructions

立即停止并卸载音频、归零进度，保留队列；会取消尚未完成的点歌

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": {
      "requestId": "<requestId>"
    },
    "name": "netease_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses concrete state changes: audio is unloaded, progress is reset to zero, the queue is retained, and pending song requests are canceled. This is exactly the kind of detailed behavioral context an agent needs for a mutation operation.

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

Conciseness5/5

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

It is a single compact sentence that front-loads the core action and then enumerates the key state effects. There is no filler or repetition.

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 low-complexity command with no output schema, the description is nearly complete as a behavioral specification. The main remaining gap is the unexplained requestId parameter, which is not covered anywhere else.

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?

The input schema has 0% description coverage and the description does not mention requestId at all, so its role, format, or idempotency semantics are left unexplained. The single-parameter surface limits the damage, but the description does not compensate for the schema gap.

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?

The description gives a specific verb and resource: immediately stop and unload audio, reset progress, retain the queue, and cancel unfinished song requests. This clearly separates it from pause/resume siblings by spelling out the state effects rather than just saying 'stop'.

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?

The behavior implies when to use it (a full stop that preserves the queue but discards progress and pending requests), but it never explicitly names alternatives such as pause or resume or states when-not to use it. Usage is inferable from the state effects rather than directly guided.

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