Skip to main content
Glama

Moddable Games Tools

by games.moddable.tools
OverviewDiscussionsAdmin

chess_get_opening_book

[REMOVED — engine#98] Opening book resolution is broken in Worker context. No replacement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / fen
      Removed value: -{
-  "description": "FEN string. Omit for starting position.",
-  "type": "string"
-}
    • removedInput schema / properties / variant / description
      Removed value: -"Variant key. Defaults to \"standard\"."
  2. Changed2 schema fields changed
    • changedInput schema / properties / fen / description
      Previous value: -"FEN position (omit for starting position)"New value: +"FEN string. Omit for starting position."
    • changedInput schema / properties / variant / description
      Previous value: -"Variant slug (default: standard)"New value: +"Variant key. Defaults to \"standard\"."
  3. Changed2 schema fields changed
    • changedInput schema / properties / fen / description
      Previous value: -"FEN string. Omit for starting position."New value: +"FEN position (omit for starting position)"
    • changedInput schema / properties / variant / description
      Previous value: -"Variant key. Defaults to \"standard\"."New value: +"Variant slug (default: standard)"
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently warns that the tool is broken and non-functional, which is the critical behavioral trait.

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 extremely concise, with the critical 'REMOVED' warning front-loaded. Every word earns its place.

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

Completeness5/5

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

For a broken tool with no replacement, the description fully communicates the necessary context: it is removed, broken, and should not be used. No additional detail is needed.

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 does not explain the 'variant' parameter, and schema description coverage is 0%. While the tool's brokenness makes parameters irrelevant, the definition still fails to add meaning beyond the schema.

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 identifies the tool as removed/broken, and 'Opening book resolution' indicates the intended resource/action. It distinguishes this tool from siblings by flagging it as non-functional.

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?

Explicitly states the tool is 'broken' and that there is 'No replacement,' telling the agent never to use this tool. This is clear when-not-to-use 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