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

netease-music-mcp

by luuu-h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Open local web player

open_web_player

Generate a local web player UI to search, play, pause, stop music, and view lyrics. Returns a localhost URL for instant access.

Instructions

Generate and serve a local web player UI for search/play/pause/stop and lyric context. Returns a localhost URL.

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": "open_web_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions generating and serving a web player UI and returning a URL, but does not detail side effects such as server lifecycle, resource usage, whether it blocks, or how to stop it. This is insufficient for a tool that starts a local server.

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?

The description is a single sentence that efficiently conveys the core purpose and return value. Every word serves a purpose, with no redundancy.

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

Completeness2/5

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

Despite the tool's relative simplicity (one optional parameter, no output schema), the description omits important behavioral context such as prerequisites (e.g., must be logged in?), server persistence, and how to terminate the web server. The agent may not understand the tool's operational implications.

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

Parameters1/5

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

Schema coverage is 0%, and the description does not mention the 'port' parameter at all. The schema provides constraints and a default, but the description adds no context about the parameter's purpose (e.g., that it specifies the port for the local server). This leaves the agent uninformed.

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 clearly states the tool generates and serves a local web player UI for controlling playback (search/play/pause/stop/lyrics) and returns a localhost URL. This distinguishes it from sibling tools that perform individual actions.

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 description implies the tool is for obtaining a UI for music control, but it does not explicitly state when to use it vs. using individual playback commands or when not to use it. Context can be inferred from sibling tool names, but explicit guidance is lacking.

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