Skip to main content
Glama
crates-music-mcp

crates-music-mcp

by guohangbk

ncm_liked_songs

Fetches liked songs from NetEase Cloud Music for agent workflows, preserving compatibility with legacy prompts that expect NetEase favorites.

Instructions

网易云收藏(等价于 liked_songs(service='netease'),保留是为了兼容老提示词)。

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add useful lifecycle context by declaring this a compatibility alias, but it says nothing about authentication requirements, pagination, or what limit=0 (the default) actually means, which matters for a collection-fetching call.

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?

One short sentence, front-loaded with the resource name and finished with the equivalence and compatibility rationale. Nothing is wasted and no clause is redundant.

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?

An output schema exists, so return-value documentation is not required, and the tool has only one parameter. Still, the meaning of limit=0 is an open question that neither the schema nor the description resolves, which is a real gap for an otherwise trivial tool.

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?

Schema coverage is 0% on a single parameter, so the description must compensate and it does not. The limit parameter with default 0 is never mentioned, leaving the agent to guess whether 0 means unlimited, none, or a server default.

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?

Names the resource (NetEase favorites/liked songs) and explicitly declares its equivalence to liked_songs(service='netease'), so an agent can tell exactly which dataset it returns and how it relates to a sibling. It stops short of 5 only because it never says what the returned collection contains, leaving that to the output schema.

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?

States it is retained solely for backward compatibility with old prompts, which effectively implies new usage should go through liked_songs(service='netease') instead. The guidance is clear in context but is framed as a deprecation note rather than an explicit 'prefer X, use this only when Y' instruction.

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