Skip to main content
Glama
Sign In

RoTerminal

by co.roterminal
OverviewDiscussionsAdmin

Day by day

days
Read-onlyIdempotent

One game’s players day by day (New York days, newest first): the average, peak and low, visits that day, and what happened (updates, events). Free shows the last 7 days; Pro shows every day since tracking began on Sep 27 2026.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game": "<game>"
    },
    "name": "days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back, 1 to 400 (default 14; Free sees 7)
gameYesThe game: its name (like "grow a garden"), its universe id, its Roblox link or place id, or its roterminal.co/g/ link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"How many days back, 1 to 60 (default 14; Free sees 7)"New value: +"How many days back, 1 to 400 (default 14; Free sees 7)"
  2. Changed1 schema field changed
    • changedInput schema / properties / game / description
      Previous value: -"The game: its name (like \"grow a garden\"), its universe id, or its roterminal.co/g/ link"New value: +"The game: its name (like \"grow a garden\"), its universe id, its Roblox link or place id, or its roterminal.co/g/ link"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavioral context: days are New York-timezone based, results are newest-first, and the returned window depends on the caller's plan and on a tracking start date of Sep 27 2026. It stops short of describing what happens on invalid inputs or whether days with no data are omitted.

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, no filler: the identity of the tool and its ordering/timezone are front-loaded, and the plan-based window constraint follows. Every clause carries information an agent needs.

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?

With no output schema, the description correctly takes on the burden of describing return fields (average, peak, low, visits, events) and the ordering convention, and it discloses the Free/Pro data window and tracking start date. Largely complete for a two-parameter read tool, though error/empty-result behavior is unmentioned.

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% — both parameters are documented, including the 1–400 range, default of 14, and the Free cap of 7. The description restates the Free/Pro window but adds no new syntax or format detail beyond the schema, so the baseline of 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?

"One game’s players day by day" states a specific resource (daily player metrics for a single game) and enumerates what comes back (average, peak, low, visits, events), which is far more than a restatement of the name. It does not, however, distinguish itself from plausible siblings like my_game_days or series, so an agent must infer the boundary.

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 rather than stated: the description makes clear this returns a historical daily view for one game, and the Free/Pro window note implies when results will be truncated. There is no explicit "use this instead of X when Y" guidance against siblings such as my_game_days, charts, or series.

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