Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

chess_validate_move

[DEPRECATED — use play_validate_move] Check if a chess move is legal. Removal: v1.0.0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moveYes
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / fen
      Removed value: -{
-  "description": "FEN string. Omit for starting position.",
-  "type": "string"
-}
    • removedInput schema / properties / move / description
      Removed value: -"Move in coordinate notation (e.g. \"e2e4\", \"e7e8q\" for promotion)."
    • changedInput schema / properties / move / type
      Previous value: -"string"New value: +"object"
    • removedInput schema / properties / variant / description
      Removed value: -"Variant key. Defaults to \"standard\"."
  2. Changed4 schema fields changed
    • changedInput schema / properties / fen / description
      Previous value: -"Current FEN"New value: +"FEN string. Omit for starting position."
    • changedInput schema / properties / move / description
      Previous value: -"Move to validate"New value: +"Move in coordinate notation (e.g. \"e2e4\", \"e7e8q\" for promotion)."
    • changedInput schema / properties / variant / description
      Previous value: -"Variant slug (default: standard)"New value: +"Variant key. Defaults to \"standard\"."
    • changedInput schema / required
      Previous value: -[
-  "fen",
-  "move"
-]New value: +[
+  "move"
+]
  3. Changed4 schema fields changed
    • changedInput schema / properties / fen / description
      Previous value: -"FEN string. Omit for starting position."New value: +"Current FEN"
    • changedInput schema / properties / move / description
      Previous value: -"Move in coordinate notation (e.g. \"e2e4\", \"e7e8q\" for promotion)."New value: +"Move to validate"
    • changedInput schema / properties / variant / description
      Previous value: -"Variant key. Defaults to \"standard\"."New value: +"Variant slug (default: standard)"
    • changedInput schema / required
      Previous value: -[
-  "move"
-]New value: +[
+  "fen",
+  "move"
+]
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds a useful deprecation and removal timeline, which is a behavioral trait. However, it does not disclose whether the tool is read-only, what side effects it might have, or what it returns, leaving gaps in transparency.

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 concise, consisting of two short sentences. The deprecation warning is front-loaded, and every word earns its place. It is not over-verbose or under-specified in terms of prose length.

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 has a nested object parameter, no output schema, and no annotations, so the description must be comprehensive. It provides a deprecation note but omits parameter details and return-value information. This is incomplete for actual invocation, though the deprecation guidance adds some value.

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

Parameters1/5

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

The schema has 2 parameters with no descriptions (0% coverage). The description provides no additional meaning about the 'move' object structure or the 'variant' string. It fails to compensate for the lack of parameter documentation, making parameter semantics completely inadequate.

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 the tool's function: 'Check if a chess move is legal.' This is a specific verb+resource statement. The deprecation note explicitly distinguishes it from the sibling tool play_validate_move, which is the intended replacement.

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 description explicitly states 'DEPRECATED — use play_validate_move' and specifies the removal version, providing clear when-not-to-use guidance and naming the alternative tool. This fully satisfies the criterion for explicit 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
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