Skip to main content
Glama

Roblox

by io.github.pipeworx-io

Game

game
Read-onlyIdempotent

Game (universe) detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
universe_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of game objects

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation4/5

Most tools have distinct purposes, especially within the Roblox and Pipeworx domains. However, the three variants of ask_pipeworx (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are very similar and could cause confusion, as could deep_research vs ask_pipeworx.

Naming Consistency3/5

Naming conventions are mixed: snake_case (user_followers_count), verb_noun with underscores (ask_pipeworx), and camelCase (recall, forget). Roblox tools follow a consistent 'user_' prefix, but Pipeworx tools lack a uniform pattern.

Tool Count2/5

41 tools is excessive for a server named 'Roblox'. The majority of tools are Pipeworx data utilities, which are unrelated to the server's apparent focus. This overloading undermines coherence.

Completeness3/5

Coverage within the Roblox domain is basic (user profiles, friends, games) but misses common features like asset details or group management. Pipeworx appears comprehensive for data lookups, but the overall set lacks unified domain completeness.

Resources