Moddable Games Tools

piece_gallery_search

Search the piece set gallery by name, style, or game type

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 10)
`query`	Yes	Search term (e.g. "staunton", "pixel", "shogi")
`family`	No	Filter by game family (chess, shogi, xiangqi, draughts, go, etc)

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 7, 2026

removedInput schema / properties / author

Removed value: -{
-  "description": "Filter by author name (case-insensitive partial match).",
-  "type": "string"
-}

changedInput schema / properties / family / description

Previous value: -"Filter by game family (e.g. \"chess\", \"shogi\", \"xiangqi\", \"janggi\", \"draughts\", \"go\", \"emoji\", \"oware\", \"abalone\", \"othello\", \"backgammon\", \"amazons\", \"breakthrough\", \"fairy-chess\", \"lines-of-action\", \"makruk\", \"sittuyin\", \"playing-cards\", \"togyzkumalak\")."New value: +"Filter by game family (chess, shogi, xiangqi, draughts, go, etc)"

removedInput schema / properties / license

Removed value: -{
-  "description": "Filter by SPDX license (e.g. \"MIT\", \"CC-BY-4.0\", \"CC0-1.0\", \"Apache-2.0\", \"GPL-2.0+\").",
-  "type": "string"
-}

changedInput schema / properties / limit / description

Previous value: -"Max results to return (default 20, max 96)."New value: +"Max results (default 10)"

removedInput schema / properties / playable

Removed value: -{
-  "description": "Filter to only playable sets (usable in the chess.moddable.games play UI).",
-  "type": "boolean"
-}

changedInput schema / properties / query / description

Previous value: -"Search term to match against set name, author, or ID (case-insensitive)."New value: +"Search term (e.g. \"staunton\", \"pixel\", \"shogi\")"

removedInput schema / properties / recolorable

Removed value: -{
-  "description": "Filter to only recolorable sets (SVGs support color theming).",
-  "type": "boolean"
-}

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

Changed8 schema fields changedJul 27, 2026

addedInput schema / properties / author

Added value: +{
+  "description": "Filter by author name (case-insensitive partial match).",
+  "type": "string"
+}

changedInput schema / properties / family / description

Previous value: -"Filter by game family (chess, shogi, xiangqi, draughts, go, etc)"New value: +"Filter by game family (e.g. \"chess\", \"shogi\", \"xiangqi\", \"janggi\", \"draughts\", \"go\", \"emoji\", \"oware\", \"abalone\", \"othello\", \"backgammon\", \"amazons\", \"breakthrough\", \"fairy-chess\", \"lines-of-action\", \"makruk\", \"sittuyin\", \"playing-cards\", \"togyzkumalak\")."

addedInput schema / properties / license

Added value: +{
+  "description": "Filter by SPDX license (e.g. \"MIT\", \"CC-BY-4.0\", \"CC0-1.0\", \"Apache-2.0\", \"GPL-2.0+\").",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Max results (default 10)"New value: +"Max results to return (default 20, max 96)."

addedInput schema / properties / playable

Added value: +{
+  "description": "Filter to only playable sets (usable in the chess.moddable.games play UI).",
+  "type": "boolean"
+}

changedInput schema / properties / query / description

Previous value: -"Search term (e.g. \"staunton\", \"pixel\", \"shogi\")"New value: +"Search term to match against set name, author, or ID (case-insensitive)."

addedInput schema / properties / recolorable

Added value: +{
+  "description": "Filter to only recolorable sets (SVGs support color theming).",
+  "type": "boolean"
+}

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

Changed8 schema fields changedJul 26, 2026

removedInput schema / properties / author

Removed value: -{
-  "description": "Filter by author name (case-insensitive partial match).",
-  "type": "string"
-}

changedInput schema / properties / family / description

Previous value: -"Filter by game family (e.g. \"chess\", \"shogi\", \"xiangqi\", \"janggi\", \"draughts\", \"go\", \"emoji\", \"oware\", \"abalone\", \"othello\", \"backgammon\", \"amazons\", \"breakthrough\", \"fairy-chess\", \"lines-of-action\", \"makruk\", \"sittuyin\", \"playing-cards\", \"togyzkumalak\")."New value: +"Filter by game family (chess, shogi, xiangqi, draughts, go, etc)"

removedInput schema / properties / license

Removed value: -{
-  "description": "Filter by SPDX license (e.g. \"MIT\", \"CC-BY-4.0\", \"CC0-1.0\", \"Apache-2.0\", \"GPL-2.0+\").",
-  "type": "string"
-}

changedInput schema / properties / limit / description

Previous value: -"Max results to return (default 20, max 96)."New value: +"Max results (default 10)"

removedInput schema / properties / playable

Removed value: -{
-  "description": "Filter to only playable sets (usable in the chess.moddable.games play UI).",
-  "type": "boolean"
-}

changedInput schema / properties / query / description

Previous value: -"Search term to match against set name, author, or ID (case-insensitive)."New value: +"Search term (e.g. \"staunton\", \"pixel\", \"shogi\")"

removedInput schema / properties / recolorable

Removed value: -{
-  "description": "Filter to only recolorable sets (SVGs support color theming).",
-  "type": "boolean"
-}

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

AddedJun 28, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description is the sole source of behavioral information. It discloses that the search matches name, style, or game type, but it does not describe result ordering, pagination, return format, or any side effects, leaving significant behavioral gaps.

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 states the tool's purpose. It contains no redundancy or filler.

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?

The tool is a search operation with no output schema, so the description should explain what results are returned. It only states the search action and fields, omitting any detail about response structure, sorting, or limits, making it incomplete for agent usage.

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

Parameters4/5

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

The schema already provides descriptions for all three parameters (100% coverage). The description adds semantic value by clarifying that the query can match across 'name, style, or game type', which is not explicitly stated in the schema's property description.

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 states a specific verb ('Search') and resource ('piece set gallery'), and identifies searchable fields ('by name, style, or game type'). This distinguishes it from sibling search tools like board_gallery_search and tile_gallery_search by specifying the gallery type.

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 establishes clear context by indicating this tool searches piece sets, which guides when to use it vs other gallery searches. However, it does not explicitly name alternative tools or provide exclusion criteria, so it falls short of 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 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.

piece_gallery_search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources