netease-music-mcp

Overview Schema Source Related Servers Discussions Admin

netease_status

Read-only

Reads the standalone player’s real playback position and status, indicating when playback cannot be reported as played because verification is false.

Instructions

读取独立播放器真实位置和状态，verified=false时不可报告已播放

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "netease_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Oct 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true). The description adds one genuinely new behavioral constraint about not reporting playback when verified=false, but never says where that flag comes from or what else the response contains.

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?

A single compact sentence that leads with the read purpose and then the verified caveat; no filler. It is slightly too compressed, though, because '独立播放器' and 'verified' are left unexplained.

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?

With no output schema, the description must carry the burden of telling the agent what comes back. It mentions position, status, and a verified flag, but not the shape or fields of the response, leaving the agent to discover the return format by calling it.

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

Parameters4/5

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

The tool takes zero parameters, so the schema needs no description support; baseline 4 applies. The description adds no parameter meaning, but as there are no parameters that is not a gap.

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?

States a specific verb (读取) and resource (播放器真实位置和状态), which distinguishes it from the playback-control siblings like netease_play and netease_pause. It does not explicitly contrast with netease_account_status, and '独立播放器' is jargon that is not defined.

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 clause 'verified=false时不可报告已播放' hints at a gating condition for use, but the description never says when to call this rather than netease_account_status or netease_song_detail, and never says what 'verified' refers to.

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