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

crates-music-mcp

by guohangbk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

login_start

Starts a QQ Music, NetEase, or Kugou login session after method selection, returning SMS or QR authentication steps for the user to complete.

Instructions

Start a login session. Call login_methods FIRST so the user can pick.

service: qq_music | netease | kugou method: qq_music -> phone_code（默认）| qq_qr | wx_qr | mobile_qr netease -> cookie（不用 login_start）| phone_code | qr kugou -> qr（默认）| phone_code 留空 = 用该平台推荐的方式。 phone: phone_code 必填；手机号由用户在对话里给出。

phone_code 不发二维码：login_start 发短信 -> 用户把验证码贴进对话 -> login_submit(session_id, code)。扫码方式返回 qr_markdown / ImageContent / qr_data_url，用户扫码并在手机上确认后调用 login_poll。

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

Input Schema

NameRequiredDescriptionDefault
phoneNo
ctcodeNo
methodNo
serviceNoqq_music

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that phone_code triggers an outbound SMS rather than a QR code, that QR methods return qr_markdown / ImageContent / qr_data_url, and that the user must confirm on-device before login_poll. Gaps remain around session lifetime, what happens if login_start is called repeatedly, and error/expiry behavior.

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?

Front-loaded with the one-line purpose, then a compact mapping table that packs a lot of routing information into few tokens with no filler sentences. The bilingual mixing and terse arrow notation make it slightly harder to parse, but nothing is redundant.

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 4-parameter, zero-annotation tool with no output schema, the description compensates by describing return payload shapes (qr_markdown, ImageContent, qr_data_url) and the downstream handoff. Missing session lifecycle details and the undocumented ctcode keep it from being fully complete.

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 coverage is 0%, so the description must compensate and largely does: it enumerates the service values with per-platform recommended defaults, lists valid method values per service, and states that phone is required for phone_code and is supplied by the user in conversation. The fourth parameter, ctcode, is never mentioned, leaving one of four parameters undocumented anywhere.

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?

Opens with a specific verb+resource ('Start a login session') and then delineates the two discrete flows (SMS code vs QR) that this tool can initiate. It explicitly names the sibling tools involved in each flow (login_methods first, then login_submit for codes or login_poll after scanning), so an agent can place it in the login sequence without inspecting other schemas.

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

Usage Guidelines5/5

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

Gives an explicit ordering constraint ('Call login_methods FIRST so the user can pick') and an explicit exclusion: netease via cookie does not use login_start at all. Default behavior per platform is also stated ('留空 = 用该平台推荐的方式'), leaving nothing to inference about when this tool is the right call.

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