Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

hex_get_info

Get info about a specific hex coordinate (terrain, neighbours, distance)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesHex Q coordinate (column)
rYesHex R coordinate (row)
gameNoGame context for terrain lookup
seedNoMap seed (to look up terrain from a generated map)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Game key."New value: +"Game context for terrain lookup"
    • removedInput schema / properties / layout
      Removed value: -{
-  "description": "Layout variant.",
-  "type": "string"
-}
    • removedInput schema / properties / players
      Removed value: -{
-  "description": "Player count.",
-  "type": "number"
-}
    • changedInput schema / properties / q / description
      Previous value: -"Axial q coordinate of the target hex."New value: +"Hex Q coordinate (column)"
    • changedInput schema / properties / r / description
      Previous value: -"Axial r coordinate of the target hex."New value: +"Hex R coordinate (row)"
    • changedInput schema / properties / seed / description
      Previous value: -"Seed used to generate the map."New value: +"Map seed (to look up terrain from a generated map)"
    • removedInput schema / properties / size
      Removed value: -{
-  "description": "Map size.",
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "game",
-  "q",
-  "r"
-]New value: +[
+  "q",
+  "r"
+]
  2. Changed8 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Game context for terrain lookup"New value: +"Game key."
    • addedInput schema / properties / layout
      Added value: +{
+  "description": "Layout variant.",
+  "type": "string"
+}
    • addedInput schema / properties / players
      Added value: +{
+  "description": "Player count.",
+  "type": "number"
+}
    • changedInput schema / properties / q / description
      Previous value: -"Hex Q coordinate (column)"New value: +"Axial q coordinate of the target hex."
    • changedInput schema / properties / r / description
      Previous value: -"Hex R coordinate (row)"New value: +"Axial r coordinate of the target hex."
    • changedInput schema / properties / seed / description
      Previous value: -"Map seed (to look up terrain from a generated map)"New value: +"Seed used to generate the map."
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Map size.",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "q",
-  "r"
-]New value: +[
+  "game",
+  "q",
+  "r"
+]
  3. Changed8 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Game key."New value: +"Game context for terrain lookup"
    • removedInput schema / properties / layout
      Removed value: -{
-  "description": "Layout variant.",
-  "type": "string"
-}
    • removedInput schema / properties / players
      Removed value: -{
-  "description": "Player count.",
-  "type": "number"
-}
    • changedInput schema / properties / q / description
      Previous value: -"Axial q coordinate of the target hex."New value: +"Hex Q coordinate (column)"
    • changedInput schema / properties / r / description
      Previous value: -"Axial r coordinate of the target hex."New value: +"Hex R coordinate (row)"
    • changedInput schema / properties / seed / description
      Previous value: -"Seed used to generate the map."New value: +"Map seed (to look up terrain from a generated map)"
    • removedInput schema / properties / size
      Removed value: -{
-  "description": "Map size.",
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "game",
-  "q",
-  "r"
-]New value: +[
+  "q",
+  "r"
+]
  4. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must fully convey behavioral semantics. It states the action 'Get info' (implying read-only), but does not disclose prerequisites (e.g., whether game/seed are needed for terrain lookup), the exact return structure, or side effects. This is insufficient 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?

The description is a single, concise sentence that immediately conveys the core function and relevant details, with no superfluous words.

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?

Given no output schema, the description partially addresses return contents (terrain, neighbours, distance) but leaves gaps: 'distance' is ambiguous (distance to what?), and the optional parameters game and seed are not explained in terms of necessity or impact. The tool is simple but not fully specified.

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 coverage is 100%, so descriptions for all parameters exist. The tool description adds no additional meaning beyond listing the output fields (terrain, neighbours, distance), which does not directly explain parameter behavior. Baseline 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 clearly identifies the tool's purpose: retrieving info about a specific hex coordinate, listing the exact data (terrain, neighbours, distance). This distinguishes it from sibling tools like hex_pathfind or hex_compute_fov, which focus on other aspects.

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 implies use when one needs coordinate-based hex info, but it doesn't explicitly mention when to prefer this tool over alternatives like hex_pathfind or hex_compute_fov. No exclusions or alternative guidance is provided.

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