Skip to main content
Glama

AutoTasker Hub — China Social Data API

netease_hot

NetEase Cloud Music hot song list (网易云热歌榜) with popularity scores. $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": "netease_hot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 disclose the meaningful behavioral fact that each call costs $0.02 USDC, which matters for a paid tool. However, it says nothing about ordering, rate limits, authentication/USDC payment mechanics, or how large a response the limit produces.

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?

One compact sentence that front-loads what the tool returns and ends with the cost, with no filler. It is terse to the point of under-specification, but nothing in it is wasted.

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 simple single-optional-parameter read tool with no output schema, the description conveys the source, the payload concept, and the price, which is the minimum an agent needs to decide to call it. It stops short of describing result ordering, item fields, or pagination behavior that would make it self-sufficient.

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?

The single parameter (limit, default 10, max 50) is never mentioned in the description, and schema description coverage is 0%, so nothing clarifies whether limit is a hard cap, what happens above 50, or whether results are ordered by the popularity score. The description does not compensate for the coverage gap.

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 a specific resource (NetEase Cloud Music hot song list, with the Chinese name for disambiguation) and states what it returns (popularity scores). An agent can distinguish it from baidu_hot/douyin_hot/juejin_hot because the source platform is named explicitly, though the description never states that these siblings cover other platforms.

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?

The description gives no when-to-use or when-not-to-use guidance and no alternatives (e.g., other *_hot tools for other platforms). The only usage-relevant fact is the price, leaving the agent to infer context from the tool name alone.

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.