Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

nukes_setup_generator

Generate random territory/resource setup for a Nukes game

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playersNoNumber of players (2-6, default: 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / players / description
      Previous value: -"Number of players (2-6). Defaults to 3."New value: +"Number of players (2-6, default: 2)"
    • removedInput schema / properties / seed
      Removed value: -{
-  "description": "Map seed for reproducible setups.",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • changedInput schema / properties / players / description
      Previous value: -"Number of players (2-6, default: 2)"New value: +"Number of players (2-6). Defaults to 3."
    • addedInput schema / properties / seed
      Added value: +{
+  "description": "Map seed for reproducible setups.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / players / description
      Previous value: -"Number of players (2-6). Defaults to 3."New value: +"Number of players (2-6, default: 2)"
    • removedInput schema / properties / seed
      Removed value: -{
-  "description": "Map seed for reproducible setups.",
-  "type": "string"
-}
  4. Added

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states that it generates a random setup, but gives no details about the return format, side effects, or whether it is a pure read-only operation.

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, front-loaded sentence with no filler or redundant information. 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?

The tool is simple with one optional parameter, and the schema handles parameter details. However, there is no output schema and the description does not explain what a 'territory/resource setup' includes, leaving some ambiguity about the return value.

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?

The input schema fully documents the single 'players' parameter with its range (2-6) and default value (2), so the description does not need to add much. Since schema coverage is 100%, the baseline score of 3 is appropriate.

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 uses a specific verb ('Generate') and a clear resource ('random territory/resource setup for a Nukes game'), which makes the tool's function immediately obvious. It distinguishes itself from sibling tools like game_nukes_combat by focusing on setup generation rather than combat.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is used for setting up a Nukes game, but it does not mention exclusions or alternative tools.

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