Moddable Games Tools

oracle_encounter

Generate a tabletop RPG encounter with CR-appropriate monsters, terrain, and loot (D&D 5e or Pathfinder 1e)

Input Schema

TableJSON Schema

Name	Required	Description
`system`	No	Game system (default: dnd-5e)
`terrain`	No	Terrain type (omit for random)
`difficulty`	No	Encounter difficulty (default: medium)
`party_size`	No	Number of players 1-10 (default: 4)
`party_level`	No	Average party level 1-20 (default: 5)
`monster_type`	No	Filter by type (undead, dragon, beast, etc)

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedAug 7, 2026

changedInput schema / properties / difficulty / description

Previous value: -"Encounter difficulty. Defaults to \"medium\"."New value: +"Encounter difficulty (default: medium)"

removedInput schema / properties / loot_tier

Removed value: -{
-  "description": "Loot rarity tier. Defaults to \"medium\".",
-  "enum": [
-    "none",
-    "low",
-    "medium",
-    "high",
-    "legendary"
-  ],
-  "type": "string"
-}

changedInput schema / properties / monster_type / description

Previous value: -"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\")."New value: +"Filter by type (undead, dragon, beast, etc)"

changedInput schema / properties / party_level / description

Previous value: -"Average party level (1-20). Defaults to 5."New value: +"Average party level 1-20 (default: 5)"

changedInput schema / properties / party_size / description

Previous value: -"Number of players (1-10). Defaults to 4."New value: +"Number of players 1-10 (default: 4)"

changedInput schema / properties / system / description

Previous value: -"Game system. Defaults to \"dnd-5e\"."New value: +"Game system (default: dnd-5e)"

changedInput schema / properties / terrain / description

Previous value: -"Terrain type (e.g. \"Forest\", \"Cavern\"). Omit for random."New value: +"Terrain type (omit for random)"

Changed7 schema fields changedJul 27, 2026

changedInput schema / properties / difficulty / description

Previous value: -"Encounter difficulty (default: medium)"New value: +"Encounter difficulty. Defaults to \"medium\"."

addedInput schema / properties / loot_tier

Added value: +{
+  "description": "Loot rarity tier. Defaults to \"medium\".",
+  "enum": [
+    "none",
+    "low",
+    "medium",
+    "high",
+    "legendary"
+  ],
+  "type": "string"
+}

changedInput schema / properties / monster_type / description

Previous value: -"Filter by type (undead, dragon, beast, etc)"New value: +"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\")."

changedInput schema / properties / party_level / description

Previous value: -"Average party level 1-20 (default: 5)"New value: +"Average party level (1-20). Defaults to 5."

changedInput schema / properties / party_size / description

Previous value: -"Number of players 1-10 (default: 4)"New value: +"Number of players (1-10). Defaults to 4."

changedInput schema / properties / system / description

Previous value: -"Game system (default: dnd-5e)"New value: +"Game system. Defaults to \"dnd-5e\"."

changedInput schema / properties / terrain / description

Previous value: -"Terrain type (omit for random)"New value: +"Terrain type (e.g. \"Forest\", \"Cavern\"). Omit for random."

Changed7 schema fields changedJul 26, 2026

changedInput schema / properties / difficulty / description

Previous value: -"Encounter difficulty. Defaults to \"medium\"."New value: +"Encounter difficulty (default: medium)"

removedInput schema / properties / loot_tier

Removed value: -{
-  "description": "Loot rarity tier. Defaults to \"medium\".",
-  "enum": [
-    "none",
-    "low",
-    "medium",
-    "high",
-    "legendary"
-  ],
-  "type": "string"
-}

changedInput schema / properties / monster_type / description

Previous value: -"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\")."New value: +"Filter by type (undead, dragon, beast, etc)"

changedInput schema / properties / party_level / description

Previous value: -"Average party level (1-20). Defaults to 5."New value: +"Average party level 1-20 (default: 5)"

changedInput schema / properties / party_size / description

Previous value: -"Number of players (1-10). Defaults to 4."New value: +"Number of players 1-10 (default: 4)"

changedInput schema / properties / system / description

Previous value: -"Game system. Defaults to \"dnd-5e\"."New value: +"Game system (default: dnd-5e)"

changedInput schema / properties / terrain / description

Previous value: -"Terrain type (e.g. \"Forest\", \"Cavern\"). Omit for random."New value: +"Terrain type (omit for random)"

Changed2 schema fields changedJul 22, 2026

changedInput schema / properties / monster_type / description

Previous value: -"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\", \"Outsider\", \"Construct\"). Omit for any."New value: +"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\")."

changedInput schema / properties / terrain / description

Previous value: -"Terrain type (e.g. \"Forest\", \"Cavern\", \"Dungeon\"). Omit for random."New value: +"Terrain type (e.g. \"Forest\", \"Cavern\"). Omit for random."

Changed2 schema fields changedJul 22, 2026

changedInput schema / properties / monster_type / description

Previous value: -"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\"). Omit for any."New value: +"Filter monsters by type (e.g. \"undead\", \"dragon\", \"beast\", \"Outsider\", \"Construct\"). Omit for any."

addedInput schema / properties / system

Added value: +{
+  "description": "Game system. Defaults to \"dnd-5e\".",
+  "enum": [
+    "dnd-5e",
+    "pathfinder-1e"
+  ],
+  "type": "string"
+}

AddedJul 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the output includes CR-appropriate monsters, terrain, and loot, but it does not explain return format, randomness, how party_level/difficulty affect CR, or any failure modes. The description adds some behavioral context but lacks depth for a tool with zero annotation support.

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 sentence, front-loaded with the action ('Generate'), and every word contributes meaning. It packs key information (output elements, systems) without any filler or redundancy.

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 description conveys the core function but is incomplete for a tool with 6 optional parameters and no output schema. It doesn't clarify what the returned encounter looks like (e.g., full statblocks, names only), how parameters interact, or how it differs from near-sibling rpg_random_encounter. The schema fills parameter details, but the lack of output schema and sibling differentiation leaves gaps.

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%, so the baseline is 3. The description does not add any parameter-specific semantics beyond what the schema already documents (e.g., it doesn't explain how terrain or monster_type filters work). It relies entirely on the schema for parameter meaning.

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' with a clear resource ('tabletop RPG encounter') and specifies output components (CR-appropriate monsters, terrain, loot) plus supported systems (D&D 5e / Pathfinder 1e). This clearly distinguishes it from generic oracle tools like oracle_scene or oracle_ask, and even from rpg_random_encounter which lacks the specificity of CR-appropriate and loot.

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?

The description states what the tool does, so usage is implied (when you need an encounter). However, it provides no explicit guidance on when to use this tool versus similar siblings like rpg_random_encounter or oracle_scene, nor does it mention any exclusions or alternatives.

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

oracle_encounter

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources