Skip to main content
Glama

AutoTasker Hub — China Social Data API

thepaper_hot

The Paper (澎湃新闻) hot news ranking with interaction counts. $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": "thepaper_hot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful behavioral facts — the request is paid ($0.02 USDC) and each item carries interaction counts — but says nothing about update cadence, ordering, pricing failure modes, or return shape beyond 'ranking'.

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?

Two short sentences, both carrying unique information: what is returned and what it costs. Nothing is wasted and the identifying detail is front-loaded.

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 low-complexity, zero-required-param, no-output-schema tool this is close to adequate — source, content type, and cost are covered. The undocumented limit parameter and the absence of freshness/ordering context leave clear gaps.

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?

One optional parameter (limit, default 10, max 20) with 0% schema description coverage, and the description never mentions it. An agent gets no signal that result count is tunable or that 20 is the ceiling.

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?

States a specific resource and source: hot news ranking from The Paper (澎湃新闻), returning interaction counts. Naming the outlet implicitly distinguishes it from siblings like baidu_hot, douyin_hot and netease_hot, though it never explicitly contrasts them.

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?

No when-to-use or when-not-to-use guidance, no mention of what distinguishes this source from the other *_hot siblings, and no note that the call is paid before invoking. Usage is only inferable from the source name.

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.