Skip to main content
Glama

AutoTasker Hub — China Social Data API

trend_predict

Run trend prediction engine: top topics with velocity scores. $0.01 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": "trend_predict"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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, and the disclosure that each call costs $0.01 USDC is genuinely useful behavioral context an agent would not otherwise know. Beyond that, it says nothing about data freshness, whether the prediction is model-generated versus aggregated, or how payment is handled, so the transparency is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler and the core function stated first, which is structurally sound. The terseness tips into under-specification rather than efficient density, since the fragments leave key questions unanswered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-annotation, no-output-schema tool, the description should at least explain the limit parameter, the source of the trends, and the rough shape of a result beyond 'topics with velocity scores'. None of that is present, and the payment flow is stated as a price without any indication of how a call is billed or authorized.

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% for the single parameter; the schema only supplies a default of 5 and a maximum of 20 with no textual description. The description never mentions 'limit' or clarifies that it caps the number of topics returned, leaving the agent to infer its meaning from the property name alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Run trend prediction engine') and names the output ('top topics with velocity scores'), so the general function is inferable. However, it never says which trend domain or data source is used, and with siblings like baidu_hot and douyin_hot in the family, an agent cannot tell what makes this prediction engine different from a plain hot-list tool.

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, when not to, or what alternative to pick for simpler hot-list needs. The only contextual detail is the price, which informs cost decisions but not tool selection.

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.