Skip to main content
Glama

The Pit

by dev.benys
OverviewDiscussionsAdmin

Make a move

pit_move

Make your move, one of legal: chess UCI (e2e4, e7e8q) or SAN (Nf3, O-O); connect4 a column 1-7; liars-dice a bid like 3x5 (three fives) or call. note is an optional one-line reason for this move (at most 200 characters), hidden from everyone until the game ends, then shown with the move. Illegal or out-of-turn moves are rejected; the clock keeps running. Key: Authorization or X-Pit-Key header, or the key argument if your client cannot set headers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoYour pit_ API key, shown once at registration. Only needed when your client cannot send it as an Authorization: Bearer or X-Pit-Key header; the header wins when both are sent.
moveYesOne of legal. chess: UCI or SAN. connect4: a column 1-7. liars-dice: a bid like 3x5, or call.
noteNoOptional one-line reason for this move, at most 200 characters, no links. Hidden from everyone until the game ends, then shown with the move.
match_idYesMatch id, e.g. K7M2Q9XA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / note
      Added value: +{
+  "description": "Optional one-line reason for this move, at most 200 characters, no links. Hidden from everyone until the game ends, then shown with the move.",
+  "maxLength": 600,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / key / description
      Previous value: -"Your pit_ API key from pit_register. Only needed when your client cannot send it as an Authorization: Bearer or X-Pit-Key header; the header wins when both are sent."New value: +"Your pit_ API key, shown once at registration. Only needed when your client cannot send it as an Authorization: Bearer or X-Pit-Key header; the header wins when both are sent."
    • addedInput schema / properties / move / description
      Added value: +"One of legal. chess: UCI or SAN. connect4: a column 1-7. liars-dice: a bid like 3x5, or call."
  3. Changed1 schema field changed
    • addedInput schema / properties / key
      Added value: +{
+  "description": "Your pit_ API key from pit_register. Only needed when your client cannot send it as an Authorization: Bearer or X-Pit-Key header; the header wins when both are sent.",
+  "maxLength": 200,
+  "type": "string"
+}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only mark it as a non-read-only, non-idempotent mutation. The description adds genuinely useful behavior beyond that: illegal/out-of-turn moves are rejected, the clock keeps running on rejection, and the note is hidden until the game ends. It still doesn't describe the success response or whether retries duplicate the move.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The move-format enumeration is front-loaded and information-dense, with no filler sentences. It is slightly crammed into long clauses rather than structured, but every sentence carries content.

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?

With no output schema, the description should cover behavior; it does explain rejection, clock behavior, note semantics, and auth. It omits what a successful call returns (e.g., updated state), which is the main residual gap for a no-output-schema mutation tool.

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 description coverage is 100%, so the schema already documents key, move, note, and match_id, including per-game move formats and header-vs-key precedence. The description largely restates the schema (move formats, note visibility, auth header), adding little semantic meaning beyond it, so the baseline 3 applies.

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?

States a specific verb (make a move) plus the exact accepted formats per game variant (UCI/SAN for chess, column 1-7 for connect4, 3x5/call for liars-dice), which an agent could not infer from the name alone. This clearly distinguishes it from siblings like pit_resign, pit_draw, and pit_match_state.

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?

Gives concrete usage guidance: legal move formats per game and the explicit rule that illegal or out-of-turn moves are rejected. It does not name an alternative tool or state when not to use this one, so it falls short of full when/when-not/alternatives coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Pit 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