Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

rules_random

Get a random game suggestion from the library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playersNoNumber of players available
maxDurationNoMaximum game duration in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / family
      Removed value: -{
-  "description": "Optional game family slug to pick a random variant from (e.g. \"backgammon\" for a random backgammon variant).",
-  "type": "string"
-}
    • addedInput schema / properties / maxDuration
      Added value: +{
+  "description": "Maximum game duration in minutes",
+  "type": "number"
+}
    • addedInput schema / properties / players
      Added value: +{
+  "description": "Number of players available",
+  "type": "number"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / family
      Added value: +{
+  "description": "Optional game family slug to pick a random variant from (e.g. \"backgammon\" for a random backgammon variant).",
+  "type": "string"
+}
    • removedInput schema / properties / maxDuration
      Removed value: -{
-  "description": "Maximum game duration in minutes",
-  "type": "number"
-}
    • removedInput schema / properties / players
      Removed value: -{
-  "description": "Number of players available",
-  "type": "number"
-}
  3. Changed3 schema fields changed
    • removedInput schema / properties / family
      Removed value: -{
-  "description": "Optional game family slug to pick a random variant from (e.g. \"backgammon\" for a random backgammon variant).",
-  "type": "string"
-}
    • addedInput schema / properties / maxDuration
      Added value: +{
+  "description": "Maximum game duration in minutes",
+  "type": "number"
+}
    • addedInput schema / properties / players
      Added value: +{
+  "description": "Number of players available",
+  "type": "number"
+}
  4. Added

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states the action (get random suggestion) without explaining return format, how parameters affect the randomness, or whether it is a read-only operation. For a tool with no annotation coverage, this is minimal disclosure.

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?

The description is a single concise sentence with no filler, front-loading the purpose. It is appropriately sized for the tool's simplicity.

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?

While simple and with good schema coverage, the description omits details about return value and parameter interplay (e.g., are players/duration filters?). Without annotations or output schema, these gaps make it only minimally complete.

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 description coverage is 100%: both 'players' and 'maxDuration' have clear descriptions. The tool description adds no additional parameter context, so it scores baseline 3 per the rubric.

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 'Get a random game suggestion from the library' uses a specific verb ('get') and clarifies the resource (random game suggestion). It clearly distinguishes itself from sibling tools like rules_search and rules_get_game by emphasizing randomness.

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 when-to-use guidance is provided. It does not mention alternatives for structured search (e.g., rules_search) or listing games (rules_list_games), nor does it explain under what circumstances a random suggestion is preferred. The intended use case is only implied by the word 'random'.

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

All Moddable Games Tools 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