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

netease-music-mcp

by xinyu68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

netease_lyrics

Read-only

Retrieve timestamped lyrics by song ID for synchronized display in music interfaces; use it to show lyrics independently of playback status.

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": {
      "songId": "<songId>"
    },
    "name": "netease_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
songIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.3/5.0
Behavior3/5

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

注解已声明 readOnlyHint=true、destructiveHint=false 和 openWorldHint=true，给出了基本安全轮廓。描述补充了返回内容性质（带时间戳歌词）和不是播放状态，但没有说明鉴权、速率限制或输出结构等额外行为细节。

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?

描述极简，两个分句直接前置核心用途和排除条件，没有冗余内容。对于低复杂度工具，这个长度是合适的。

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?

工具复杂度低且无输出 schema，描述说明了返回带时间戳歌词，基本够用。但由于 songId 未解释、输出是否分页或包含哪些字段未说明，对于 agent 完整调用仍存在小缺口。

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?

唯一参数 songId 在 schema 中只有类型和正则，schema description coverage 为 0%。描述完全没有解释 songId 的语义或格式要求，未能补偿 schema 文档缺口；只能依赖参数名本身推断。

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?

状态了具体动作和资源：读取带时间戳歌词用于显示。它还通过“不是播放状态”与 netease_status 做了区分，这对兄弟工具选择很有帮助；不过未提及可能与 netease_song_detail 之类工具的重叠关系。

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?

“不是播放状态”提供了使用排除线索，让 agent 在需要播放状态时转向 netease_status。但没有明确说明何时应优先使用本工具而非 netease_song_detail，也没有说明调用前提。

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