Skip to main content
Glama

RBX Invest Roblox Limiteds market data

by com.rbxinvest
OverviewDiscussionsAdmin

Rank tracked Limited portfolios

rank_players

The biggest Roblox Limited portfolios RBX Invest tracks, by total RAP held, copies held, distinct Limited items owned, or Robux donated in the RBX Invest plaza. This covers people who signed up on RBX Invest and linked a Roblox account, not every Roblox player, so a rank from it is a rank on this board rather than a global one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
metricNovalue = total RAP held, copies = number of copies held, items = distinct Limited asset IDs held (each counts once), sponsor = everyone who has donated Robux in the RBX Invest plaza on Roblox, including players whose portfolio is not public here, by all-time Robux donated; each row has robux_donated and the sponsor rank (equal totals share a rank). Check status: unavailable means the requested ranking is not ready.value
offsetNoRows to skip, for reading past the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / metric / description
      Previous value: -"value = total RAP held, copies = number of copies held, items = distinct Limited asset IDs held (each counts once), growth = copy-weighted average lifetime appreciation (3+ copies required). Check status: unavailable means the requested ranking is not ready."New value: +"value = total RAP held, copies = number of copies held, items = distinct Limited asset IDs held (each counts once), sponsor = everyone who has donated Robux in the RBX Invest plaza on Roblox, including players whose portfolio is not public here, by all-time Robux donated; each row has robux_donated and the sponsor rank (equal totals share a rank). Check status: unavailable means the requested ranking is not ready."
    • changedInput schema / properties / metric / enum
      Previous value: -[
-  "value",
-  "copies",
-  "items",
-  "growth"
-]New value: +[
+  "value",
+  "copies",
+  "items",
+  "sponsor"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / metric / description
      Previous value: -"value = total RAP held, copies = number of copies held, growth = average lifetime appreciation across holdings (only players holding 3 or more copies are ranked)."New value: +"value = total RAP held, copies = number of copies held, items = distinct Limited asset IDs held (each counts once), growth = copy-weighted average lifetime appreciation (3+ copies required). Check status: unavailable means the requested ranking is not ready."
    • changedInput schema / properties / metric / enum
      Previous value: -[
-  "value",
-  "copies",
-  "growth"
-]New value: +[
+  "value",
+  "copies",
+  "items",
+  "growth"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / maximum
      Previous value: -25New value: +100
  4. First observed

TDQS

A3.6/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 behavioral burden. It does disclose a meaningful trait beyond the schema: the board covers only RBX Invest sign-ups with linked Roblox accounts, so ranks are board-local, not global. It says nothing about return format, pagination behavior, or the 'status: unavailable' state that the schema enum mentions.

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?

Two sentences, with the core ranking statement front-loaded before the scope caveat. It is efficient, though the second sentence is somewhat discursive and could have been tightened.

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?

No annotations and no output schema, so the description should ideally describe the shape of a result row (rank, holdings, robux_donated). The scope caveat is valuable, but without any description of return values or paging semantics, the definition is only minimally complete for a ranking endpoint.

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 67%, so the baseline is 3. The description loosely maps the metrics to plain language (total RAP held, copies held, distinct items, Robux donated), which helps interpret 'value' and 'sponsor', but the schema's enum description already spells these out more precisely, so the description is largely redundant rather than additive.

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

Purpose5/5

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

The description states a specific verb (rank) and resource (Roblox Limited portfolios tracked by RBX Invest), and enumerates the four ranking metrics, so an agent can distinguish it from rank_creators at a glance. It also scopes the population being ranked, which sharpens the purpose rather than restating the title.

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 (get a leaderboard of tracked portfolios) and importantly clarifies the eligible population, which affects whether a result is worth using. However, it never says when to choose this over rank_creators or how limit/offset interact with paging, so no explicit when/when-not guidance or alternative routing is given.

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

All RBX Invest Roblox Limiteds market data toolsInspect
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