Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools

chess_render_svg

[DEPRECATED — use play_render_board] Render a chess position as SVG. Removal: v1.0.0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fenNoFEN position string
variantNo
highlightsNoSquares to highlight (e.g. ["e2","e4"])

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / fen
      Added value: +{
+  "description": "FEN position string",
+  "type": "string"
+}
    • addedInput schema / properties / highlights
      Added value: +{
+  "description": "Squares to highlight (e.g. [\"e2\",\"e4\"])",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed5 schema fields changed
    • removedInput schema / properties / fen
      Removed value: -{
-  "description": "FEN string of the position. Omit to use the variant starting position.",
-  "type": "string"
-}
    • removedInput schema / properties / highlights
      Removed value: -{
-  "description": "Squares to highlight (algebraic notation, e.g. [\"e2\", \"e4\"] for last move).",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / size
      Removed value: -{
-  "description": "Board width in pixels. Height is derived from rows. Defaults to 480.",
-  "type": "number"
-}
    • removedInput schema / properties / theme
      Removed value: -{
-  "description": "Board colour theme. Defaults to \"classic\".",
-  "enum": [
-    "classic",
-    "cosmic",
-    "wood",
-    "marble",
-    "neon",
-    "minimal"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / variant / description
      Removed value: -"Variant key (e.g. \"standard\", \"grand\", \"capablanca\"). Defaults to \"standard\"."
  3. Changed7 schema fields changed
    • changedInput schema / properties / fen / description
      Previous value: -"FEN notation"New value: +"FEN string of the position. Omit to use the variant starting position."
    • removedInput schema / properties / flipped
      Removed value: -{
-  "description": "Flip board (black perspective)",
-  "type": "boolean"
-}
    • changedInput schema / properties / highlights / description
      Previous value: -"Squares to highlight (e.g. [\"e4\", \"d5\"])"New value: +"Squares to highlight (algebraic notation, e.g. [\"e2\", \"e4\"] for last move)."
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Board width in pixels. Height is derived from rows. Defaults to 480.",
+  "type": "number"
+}
    • addedInput schema / properties / theme
      Added value: +{
+  "description": "Board colour theme. Defaults to \"classic\".",
+  "enum": [
+    "classic",
+    "cosmic",
+    "wood",
+    "marble",
+    "neon",
+    "minimal"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / variant / description
      Previous value: -"Variant slug (default: standard)"New value: +"Variant key (e.g. \"standard\", \"grand\", \"capablanca\"). Defaults to \"standard\"."
    • removedInput schema / required
      Removed value: -[
-  "fen"
-]
  4. Changed7 schema fields changed
    • changedInput schema / properties / fen / description
      Previous value: -"FEN string of the position. Omit to use the variant starting position."New value: +"FEN notation"
    • addedInput schema / properties / flipped
      Added value: +{
+  "description": "Flip board (black perspective)",
+  "type": "boolean"
+}
    • changedInput schema / properties / highlights / description
      Previous value: -"Squares to highlight (algebraic notation, e.g. [\"e2\", \"e4\"] for last move)."New value: +"Squares to highlight (e.g. [\"e4\", \"d5\"])"
    • removedInput schema / properties / size
      Removed value: -{
-  "description": "Board width in pixels. Height is derived from rows. Defaults to 480.",
-  "type": "number"
-}
    • removedInput schema / properties / theme
      Removed value: -{
-  "description": "Board colour theme. Defaults to \"classic\".",
-  "enum": [
-    "classic",
-    "cosmic",
-    "wood",
-    "marble",
-    "neon",
-    "minimal"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / variant / description
      Previous value: -"Variant key (e.g. \"standard\", \"grand\", \"capablanca\"). Defaults to \"standard\"."New value: +"Variant slug (default: standard)"
    • addedInput schema / required
      Added value: +[
+  "fen"
+]
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the tool is deprecated and will be removed in v1.0.0, which is important context. It doesn't discuss return format or side effects, but for a rendering tool this is a minor gap.

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 exceptionally concise, using two sentences to convey function, deprecation, and replacement. It is front-loaded with the deprecation warning, making it highly efficient.

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

Completeness4/5

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

For a simple, deprecated rendering tool, the description covers the essential context: what it does, that it's deprecated, and what to use instead. Lack of output format details is acceptable given the tool's simplicity and deprecation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter semantics beyond the schema. Schema coverage is 67%, leaving 'variant' undocumented, and the description does not clarify it. The deprecation notice reduces the need for param details, but the description itself contributes nothing.

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 function: 'Render a chess position as SVG.' It also names the replacement tool, play_render_board, which distinguishes it from siblings and provides immediate context.

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

Usage Guidelines5/5

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

The deprecation notice explicitly says 'use play_render_board,' giving clear when-not-to-use guidance and naming the alternative. This is the strongest form of usage guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation3/5

Most tools have clear prefixes (chess_, play_, hex_, oracle_, rpg_, ti4_) that separate concerns, but overlap exists between deprecated chess_* tools and the newer play_* equivalents, plus rpg_random_encounter and oracle_encounter both generate encounters. Descriptions help disambiguate, but the redundancy could mislead agents.

Naming Consistency2/5

Many tools follow a domain_verb_noun pattern (hex_generate_map, play_get_moves, rpg_search_entities), but there are notable exceptions like dice_roll, game_deck_create, jam_status, and random_player_order that mix noun-first and verb-last conventions. The inconsistent ordering makes it harder to predict tool names.

Tool Count2/5

81 tools is excessive even for a broad games toolkit; the deprecated chess_* tools alone add unnecessary bulk. While the scope is wide, the count exceeds practical limits and could be consolidated into fewer, more focused tools.

Completeness4/5

The toolkit covers a wide variety of game needs: dice, cards, hex maps, chess, RPGs, TI4, jam management, and galleries. Minor gaps like the score tracker lacking a retrieval method and the absence of some lifecycle operations keep it from being perfect, but core workflows are well covered.

Resources