Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

roblox_rankings

Retrieve Roblox game rankings by shelf: top-trending, up-and-coming, top-playing-now, fun-with-friends, or top-revisited. Returns a public game shelf as JSON.

Instructions

List Roblox game rankings. Returns a public Roblox game shelf. Allowed sort_id values: top-trending, up-and-coming, top-playing-now, fun-with-friends, top-revisited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_idNoRanking shelf: top-trending, up-and-coming, top-playing-now, fun-with-friends, top-revisited

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort_id / enum
      Added value: +[
+  "top-trending",
+  "up-and-coming",
+  "top-playing-now",
+  "fun-with-friends",
+  "top-revisited"
+]
  2. Addedv1.16.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is public and returns a shelf, but does not state read-only behavior explicitly, pagination, authentication needs, or default behavior when sort_id is omitted. This is thin for an unannotated tool.

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 sentences carry all essential information: the action, the return type, and the permissible parameter values. No filler or repetition.

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 list endpoint with one optional parameter and no output schema, the description covers the basic purpose and allowed values. It lacks detail on the structure of the 'shelf' or any result shape, but given the low complexity and high schema coverage, it is minimally sufficient.

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 coverage is 100% and the schema already defines the sort_id enum with the same values. The description's listing of allowed sort_id values adds no new meaning; it only repeats schema information. No additional parameter guidance is provided, so baseline 3 applies.

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 states a specific verb and resource ('List Roblox game rankings') and clarifies the result as a 'public Roblox game shelf'. It does not explicitly differentiate from sibling tools like roblox_search or roblox_game, but the wording makes its niche clear.

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?

The description implies usage (use when you want rankings) and enumerates allowed sort_id values, but provides no explicit guidance on when to choose this over alternatives like roblox_search or roblox_game, nor any exclusions. This is implied usage with no proactive routing.

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

Deploy Server

Other Tools