Skip to main content
Glama

AutoTasker Hub — China Social Data API

qqmusic_toplist

QQ Music peak charts (巅峰榜·热歌): rank, song, artist, album, duration. $0.02 USDC.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
topIdNo26=hot songs, 4=new songs, 27=original

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 disclosure burden. It does add genuinely useful behavioral context by stating the cost ($0.02 USDC) and by enumerating the payload fields, but it omits pagination behavior, whether the call has side effects, and how defaults are applied.

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?

Two short sentences with the resource and payload front-loaded and no filler. The chart's Chinese name is a useful disambiguator, though the pricing line could be considered tangential to tool selection.

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 two-optional-parameter read tool with no output schema, the definition covers what the tool returns and what it costs. Only the semantics of the limit parameter and any pagination behavior are left implicit, which is a minor gap at this complexity level.

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

Parameters3/5

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

Schema description coverage is 50%: topId is documented inline with its accepted values (26=hot songs, 4=new songs, 27=original), while limit has a self-evident default of 10 and maximum of 50. The description itself says nothing about parameters, so it neither compensates for nor extends the structured schema.

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 resource ('QQ Music peak charts (巅峰榜·热歌)') and enumerates the returned fields (rank, song, artist, album, duration), so the agent knows exactly what it gets. It does not distinguish itself from any sibling, but none of the listed siblings are competing music-chart tools.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, nor any preconditions or exclusions. Usage is only implied by the chart name, leaving the agent to infer that this is the tool for top-song rankings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.