Wieldr game radar

Get trending games

get_trending_games

Read-onlyIdempotent

Games getting the most TikTok views right now (Roblox, Steam): TikTok views of videos PUBLISHED in the last 7 or 30 days (by publish date, not views gained), with 2+ distinct creators, crossed with players online and 24 h growth. Badges: hype_over_players (attention ahead of players), viral_and_growing (top views and players rising, never a game in decline), new_and_viral (14 days old or less). state=warming_up means coverage is still thin. network=youtube lists YouTube videos one by one with their own view count (never summed or ranked per game). Unreleased games are rare. Only games Wieldr already tracks are probed for videos. Every game carries asOf (export time, UTC), source and grade (grade = completeness of the game record (A = 8+ of 10 data points known, B = 6-7, C = 4-5, D = fewer); estimate grade: B = tighter range, C = wide range, D = very rough order of magnitude.) Revenue figures are estimates with a range and a grade, never measured sales and never a guarantee. Definitions: resource wieldr://methodology.

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

Input Schema

Name	Required	Description
`sort`	No	views (default), viewsPerDay (average daily views since publication) or creators.
`badge`	No	Only games with this badge.
`limit`	No	How many results per page (default 10, max 25).
`niche`	No	Niche label, key or keyword: a ranked Roblox or Fortnite niche (e.g. "Ragdoll", "Tycoon", from list_niches), a genre (e.g. "Simulation") or a word in game titles (e.g. "brainrot").
`cursor`	No	nextCursor from the previous call, to get the next page. Omit for the first page.
`status`	No	released, early_access (Steam) or unreleased (rare). Omit for all.
`window`	No	Publish window of the videos: 7d (default) or 30d.
`network`	No	tiktok (default: ranked games) or youtube (list of videos with their raw view counts).
`platform`	No	roblox or steam (the platforms probed for videos). Omit for both.
`maxPlayers`	No	Maximum players online now (small games getting attention).
`minCreators`	No	Minimum distinct TikTok creators in the window (default 2).

Output Schema

Name	Required	Description
`asOf`	Yes	Export time, UTC (ISO 8601).
`note`	No
`sort`	No
`games`	Yes
`state`	Yes	warming_up = fewer ranked games than the threshold (coverage still thin).
`method`	No	One useful sentence; full definitions in the MCP resource wieldr://methodology.
`videos`	Yes
`window`	Yes
`dataset`	Yes	full radar (Pro or Studio key) or free preview (no key).
`matched`	Yes
`network`	Yes
`coverage`	No
`returned`	Yes
`nextCursor`	Yes	Pass it back as cursor for the next page; null = last page.
`statusNote`	No
`previewNote`	No	Free preview only: what is missing, with real counts, and where to get the full radar.
`youtubeNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses important behavior: views are based on publish date rather than views gained, 2+ distinct creators are required, state=warming_up means thin coverage, YouTube results are unranked individual videos, only tracked games are probed, and grades/asOf/source are explained. It also clarifies that revenue figures are estimates with ranges and grades, not measured sales.

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?

The opening is front-loaded and directly states the tool's purpose, and most sentences carry relevant caveats. However, the description is a dense run-on paragraph with nested parentheticals and grade definitions, making it harder to scan than necessary.

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?

Given the 11 optional parameters, annotations, and output schema, the description covers the key data semantics, caveats, and output-field meanings that an agent would otherwise miss. It is complete enough to call correctly, though the lack of explicit sibling routing keeps it from the top score.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines all parameters. The description still adds useful meaning for several parameters, especially window (publish-date views over 7 or 30 days, not views gained), network (YouTube returns raw video lists rather than ranked games), badge semantics, and the 2+ creators threshold.

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 clearly states the resource and scope: games getting the most TikTok views right now across Roblox and Steam, with view windows crossed against players online and growth. It distinguishes itself from video-list siblings by emphasizing ranked games, but it does not explicitly name or route away from siblings like get_viral_videos or find_emerging_games.

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

Usage Guidelines3/5

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

Usage is implied by the opening phrase and by filters such as network=youtube listing videos individually rather than ranked games. However, there is no explicit when-to-use guidance, when-not-to-use guidance, or named alternative among the many sibling tools.

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

All Wieldr game radar tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?