Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

ti4_draw_objectives

Draw random public objectives for TI4

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber to draw (default: 5)
stageNoStage 1 or 2 (default: both)
expansionsNoExpansion filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of objectives to draw (default 5)."New value: +"Number to draw (default: 5)"
    • changedInput schema / properties / expansions / description
      Previous value: -"Expansions to include: \"base\", \"pok\", \"ds\", \"te\". Defaults to [\"base\",\"pok\"]."New value: +"Expansion filter"
    • changedInput schema / properties / stage / description
      Previous value: -"Stage 1 or Stage 2. Defaults to 1."New value: +"Stage 1 or 2 (default: both)"
  2. Changed3 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Number to draw (default: 5)"New value: +"Number of objectives to draw (default 5)."
    • addedInput schema / properties / expansions
      Added value: +{
+  "description": "Expansions to include: \"base\", \"pok\", \"ds\", \"te\". Defaults to [\"base\",\"pok\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / stage / description
      Previous value: -"Stage 1 or 2 (default: both)"New value: +"Stage 1 or Stage 2. Defaults to 1."
  3. Changed3 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of objectives to draw (default 5)."New value: +"Number to draw (default: 5)"
    • removedInput schema / properties / expansions
      Removed value: -{
-  "description": "Expansions to include: \"base\", \"pok\", \"ds\", \"te\". Defaults to [\"base\",\"pok\"].",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • changedInput schema / properties / stage / description
      Previous value: -"Stage 1 or Stage 2. Defaults to 1."New value: +"Stage 1 or 2 (default: both)"
  4. Added

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full weight. It states the random-draw behavior but does not disclose the return format, whether expansions alter the deck, stage handling, or any side effects. This is a significant gap for an unannotated tool.

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?

One sentence of nine words communicates the core function with zero filler. It is front-loaded and efficient.

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, but the description omits the output format and how stage/expansions interact with randomness. Without annotations or an output schema, these details would help. The description is minimally adequate but has 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?

All three parameters have descriptions in the schema (100% coverage), so the description need not add parameter details. The description itself adds no semantic info about count, stage, or expansions.

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 ('draw') and resource ('random public objectives') scoped to TI4, clearly distinguishing it from sibling tools like ti4_draw_agendas or ti4_random_factions. It is concise and unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context—random public objectives for TI4—but does not explicitly name alternatives or state when not to use this tool. Since the tool name and sibling set make the use case obvious, this earns a 4 rather than a 5.

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