Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

hex_export_svg

Generate a hex map and export as SVG

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameYesGame type
seedNoRandom seed
sizeNoMap size
styleNoVisual style
hexSizeNoHex size in pixels (default: 30)
playersNoNumber of players

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / bgColor
      Removed value: -{
-  "description": "Background colour (e.g. \"#1a1a2e\"). Omit for transparent.",
-  "type": "string"
-}
    • changedInput schema / properties / game / description
      Previous value: -"Game key."New value: +"Game type"
    • changedInput schema / properties / hexSize / description
      Previous value: -"Hex radius in pixels (default from game config)."New value: +"Hex size in pixels (default: 30)"
    • removedInput schema / properties / labels
      Removed value: -{
-  "description": "Show terrain labels on hexes (default false).",
-  "type": "boolean"
-}
    • removedInput schema / properties / layout
      Removed value: -{
-  "description": "Layout variant.",
-  "type": "string"
-}
    • changedInput schema / properties / players / description
      Previous value: -"Player count."New value: +"Number of players"
    • changedInput schema / properties / seed / description
      Previous value: -"Seed used to generate the map."New value: +"Random seed"
    • changedInput schema / properties / size / description
      Previous value: -"Map size."New value: +"Map size"
    • addedInput schema / properties / style
      Added value: +{
+  "description": "Visual style",
+  "type": "string"
+}
  2. Changed9 schema fields changed
    • addedInput schema / properties / bgColor
      Added value: +{
+  "description": "Background colour (e.g. \"#1a1a2e\"). Omit for transparent.",
+  "type": "string"
+}
    • changedInput schema / properties / game / description
      Previous value: -"Game type"New value: +"Game key."
    • changedInput schema / properties / hexSize / description
      Previous value: -"Hex size in pixels (default: 30)"New value: +"Hex radius in pixels (default from game config)."
    • addedInput schema / properties / labels
      Added value: +{
+  "description": "Show terrain labels on hexes (default false).",
+  "type": "boolean"
+}
    • addedInput schema / properties / layout
      Added value: +{
+  "description": "Layout variant.",
+  "type": "string"
+}
    • changedInput schema / properties / players / description
      Previous value: -"Number of players"New value: +"Player count."
    • changedInput schema / properties / seed / description
      Previous value: -"Random seed"New value: +"Seed used to generate the map."
    • changedInput schema / properties / size / description
      Previous value: -"Map size"New value: +"Map size."
    • removedInput schema / properties / style
      Removed value: -{
-  "description": "Visual style",
-  "type": "string"
-}
  3. Changed9 schema fields changed
    • removedInput schema / properties / bgColor
      Removed value: -{
-  "description": "Background colour (e.g. \"#1a1a2e\"). Omit for transparent.",
-  "type": "string"
-}
    • changedInput schema / properties / game / description
      Previous value: -"Game key."New value: +"Game type"
    • changedInput schema / properties / hexSize / description
      Previous value: -"Hex radius in pixels (default from game config)."New value: +"Hex size in pixels (default: 30)"
    • removedInput schema / properties / labels
      Removed value: -{
-  "description": "Show terrain labels on hexes (default false).",
-  "type": "boolean"
-}
    • removedInput schema / properties / layout
      Removed value: -{
-  "description": "Layout variant.",
-  "type": "string"
-}
    • changedInput schema / properties / players / description
      Previous value: -"Player count."New value: +"Number of players"
    • changedInput schema / properties / seed / description
      Previous value: -"Seed used to generate the map."New value: +"Random seed"
    • changedInput schema / properties / size / description
      Previous value: -"Map size."New value: +"Map size"
    • addedInput schema / properties / style
      Added value: +{
+  "description": "Visual style",
+  "type": "string"
+}
  4. First observed

TDQS

C2.7/5.0
Behavior1/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 does not disclose any behavioral traits such as whether the tool returns an SVG string or writes a file, whether it requires an existing map, or any side effects. The description merely restates the action without additional context.

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 is front-loaded with the main action. Every word contributes, and it avoids unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no output schema, and no annotations, the description is too sparse. It does not explain the return format, whether the SVG is saved or returned, or how parameters influence the output. This leaves significant ambiguity for an agent trying to use the tool correctly.

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 all six parameters are described in the input schema. The description adds no additional meaning to the parameters, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a hex map and exports it as SVG, which is a specific verb+resource+format. It is distinguishable from hex_generate_map by the SVG export aspect, but the wording 'Generate a hex map and export as SVG' is slightly ambiguous about whether it only exports an existing map or creates the map from scratch, so it lacks full distinction from related tools.

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 guidance is provided about when to use this tool versus alternatives like hex_generate_map or hex_pathfind. The description simply states the function without giving context, prerequisites, or exclusions.

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