Skip to main content
Glama
Sign In

RoTerminal

by co.roterminal
OverviewDiscussionsAdmin

Roblox’s charts

charts
Read-onlyIdempotent

Roblox’s own charts (Top Earning, Top Trending, Up-and-Coming and the rest), as RoTerminal keeps them day by day in 60 countries and on every device. With no chart and no game: the list of charts, countries and devices. With a chart: its games now, each with its place yesterday, its move, its best place and its days on the chart (put a country in front for one country’s chart: jp-up-and-coming is Japan’s Up-and-Coming). With a game: every place it holds on the charts now, worldwide and in each country (like JP-Up-and-Coming #4), and each chart’s summary.

Input Schema

NameRequiredDescriptionDefault
gameNoThe game: its name (like "grow a garden"), its universe id, its Roblox link or place id, or its roterminal.co/g/ link: every place it holds on the charts now (optional)
chartNoA chart’s id, like top-earning, top-trending or up-and-coming, with a country in front for one country’s chart, like jp-up-and-coming (optional)
genreNoFor top-trending: one genre’s Trending list, like RPG or Simulation (optional)
limitNo1 to 100 (default 10)
deviceNoOne device’s chart (optional; all devices without it)
countryNoA country as two letters, like JP, BR or US (optional; worldwide without it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / chart / description
      Previous value: -"A chart’s id, like top-earning or top-trending (optional)"New value: +"A chart’s id, like top-earning, top-trending or up-and-coming, with a country in front for one country’s chart, like jp-up-and-coming (optional)"
    • addedInput schema / properties / country
      Added value: +{
+  "description": "A country as two letters, like JP, BR or US (optional; worldwide without it)",
+  "type": "string"
+}
    • addedInput schema / properties / device
      Added value: +{
+  "description": "One device’s chart (optional; all devices without it)",
+  "enum": [
+    "all",
+    "computer",
+    "phone",
+    "entry_phone",
+    "tablet",
+    "entry_tablet",
+    "console",
+    "vr"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / game
      Added value: +{
+  "description": "The game: its name (like \"grow a garden\"), its universe id, its Roblox link or place id, or its roterminal.co/g/ link: every place it holds on the charts now (optional)",
+  "type": [
+    "string",
+    "integer"
+  ]
+}
    • addedInput schema / properties / genre
      Added value: +{
+  "description": "For top-trending: one genre’s Trending list, like RPG or Simulation (optional)",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"1 to 25 (default 10)"New value: +"1 to 100 (default 10)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnly, idempotent, non-destructive, open-world false; the description adds return content: historical place yesterday, movement, best place, days on chart, country/device scoping. No auth or rate-limit notes are present, but for public read-only data this adds useful behavioral context.

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?

It front-loads the resource, then organizes by query mode, which helps parsing. The opening sentence is dense and some clauses repeat scoping details, but the content remains useful rather than padded.

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?

For a 6-param, no-output-schema tool, it explains the main modes and returns well, including historical chart data. It does not cover behavior when both chart and game are supplied, and relies on schema for limit/device details, so one minor behavioral gap remains.

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% and documents each parameter, so baseline is 3; the description adds examples and syntax beyond schema, such as jp-up-and-coming and country-prefixed chart IDs, and explains game placement output. It leaves device/limit/genre semantics mostly to schema, so not a 5.

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 the resource (Roblox charts kept by RoTerminal) and three query modes, so an agent knows it retrieves chart/game placement data. It does not explicitly differentiate this tool from siblings like top, trends, rising, or game, despite naming chart types that overlap with them.

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

Usage Guidelines4/5

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

It gives concrete mode selection: no chart/game lists charts, countries and devices; chart returns that chart's games; game returns all placements. It lacks explicit when-to-use alternatives like top or trends, but the parameter-condition routing is clear.

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

All RoTerminal 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