Skip to main content
Glama
netease-music-mcp
by xinyu68

netease_account_status

Read-only

Checks whether a NetEase Cloud Music account is logged in and whether its membership is active, without returning credentials.

Instructions

验证网易云登录及会员状态,不返回凭据

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_account_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already state that this is a read-only, non-destructive, open-world operation. Beyond those annotations, the description adds the non-obvious security guarantee that the tool will not return credentials, which is genuinely useful. It still does not say what shape the verification result takes.

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?

It is a single terse clause with no filler, and the core purpose is front-loaded. The brevity comes at the cost of leaving out the sibling differentiation the agent needs.

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?

For a zero-parameter tool with full annotation coverage and no output schema, the description covers the essentials. It omits the return shape (logged-in flag, VIP tier) and its relationship to the similarly named netease_status, which leaves the agent guessing.

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 per the rubric the baseline here is 4: there is nothing for the description to disambiguate about inputs, and the empty schema is fully self-explanatory.

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 names a specific verb-plus-resource: it verifies login and membership status. However, it does not distinguish this tool from the sibling netease_status, so an agent would still have to infer which of the two reports account and membership state.

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 use case is only implied: call this before actions that require an authenticated or VIP account. The description never states when not to use it or names any alternative, and it does not say relationship to netease_launch or netease_status.

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