crates-music-mcp

Overview Schema Source Related Servers Discussions Admin

login_methods

Lists supported login methods for QQ Music, NetEase, or Kugou so users can choose the correct account before authentication and avoid logging into an empty or wrong account.

Instructions

List every supported login method for a platform.

平台：qq_music | netease | kugou。Call this FIRST and let the user choose. QQ Music / WeChat / mobile QQ are often DIFFERENT accounts — picking the wrong one logs into an empty account. Only log into the platforms the user actually needs.

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

Input Schema

Name	Required	Description	Default
`service`	No		qq_music

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden and does add real behavioral context: account-identity pitfalls (QQ Music / WeChat / mobile QQ are different accounts) and the consequence of a wrong pick (empty account). It does not mention auth prerequisites or rate limits, but for a read-only listing this is solid added value; the output schema covers the return shape.

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?

Purpose and the required-first instruction are front-loaded, and the account-mismatch warning earns its space. The bilingual platform enumeration is compact; overall tight with minimal filler.

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 one-parameter discovery tool with an output schema, the description supplies what an agent needs: what it lists, that it must be called first, and which values are valid. Only minor gaps remain (default value, explicit handoff to login_start).

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?

Schema description coverage is 0% for the single `service` parameter, so the description must compensate — and it does by enumerating the accepted values (qq_music | netease | kugou) inline. It does not state the qq_music default or explain the platform concept further, so it is slightly incomplete rather than fully compensating.

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 opens with a specific verb and resource ('List every supported login method for a platform') and names the platform set explicitly. An agent can immediately distinguish this discovery tool from the login_start/login_submit/login_poll execution siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives strong sequencing guidance ('Call this FIRST and let the user choose') and a scope restriction ('Only log into the platforms the user actually needs'). It does not explicitly name the follow-up sibling (login_start) that consumes the choice, which keeps it just short of a full when/when-not/alternative mapping.

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