Roblox

Game

game

Read-onlyIdempotent

Game (universe) detail.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`universe_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Array of game objects

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "universe_id": 1
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Game (universe) detail response",
+  "properties": {
+    "data": {
+      "description": "Array of game objects",
+      "items": {
+        "properties": {
+          "created": {
+            "description": "Creation date (ISO 8601)",
+            "type": "string"
+          },
+          "creator": {
+            "description": "Creator information",
+            "properties": {
+              "id": {
+                "description": "Creator ID",
+                "type": "number"
+              },
+              "name": {
+                "description": "Creator name",
+                "type": "string"
+              },
+              "type": {
+                "description": "Creator type (User or Group)",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "description": {
+            "description": "Game description",
+            "type": "string"
+          },
+          "favorites": {
+            "description": "Total favorites",
+            "type": "number"
+          },
+          "id": {
+            "description": "Universe ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Game name",
+            "type": "string"
+          },
+          "playing": {
+            "description": "Currently playing count",
+            "type": "number"
+          },
+          "rootPlaceId": {
+            "description": "Root place ID",
+            "type": "number"
+          },
+          "updated": {
+            "description": "Last updated date (ISO 8601)",
+            "type": "string"
+          },
+          "visits": {
+            "description": "Total visits",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

C2/5.0

Behavior2/5

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

While annotations indicate readOnlyHint and idempotentHint, the description adds no behavioral context beyond 'detail'. It does not describe what the tool returns or any side effects, which is insufficient even with annotations present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but under-specified. It lacks structure and front-loading of key information, making it ineffective despite its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity and many sibling tools, the description is incomplete. It does not explain what 'game' or 'universe' means, nor how this tool relates to others like user_games or entity_profile.

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

Parameters2/5

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

Schema description coverage is 0%. The description implies universe_id is an identifier but adds no detail about its format, meaning, or relationship to the tool. It provides marginal value over the schema.

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

Purpose2/5

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

The description 'Game (universe) detail.' is vague and barely states the tool's function. It reuses the tool name 'Game' without a clear verb or resource, and fails to distinguish it from siblings like user_games or entity_profile.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision support.

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

All Roblox 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.