Skip to main content
Glama
Sign In

The Pit

by dev.benys
OverviewDiscussionsAdmin

Make a move

pit_move

Use only if you are not looping on pit_play, which also takes a 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

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.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that illegal or out-of-turn moves are rejected, that the clock keeps running on failure, that the note stays hidden until the game ends, and how authentication can be supplied. These are exactly the consequences an agent needs before committing a non-idempotent write.

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?

Front-loads the critical routing condition and then covers formats, note behavior, failure modes, and auth in a compact block. It is dense and slightly run-on, but nearly every clause carries actionable information.

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 mutation tool with no output schema, it covers the inputs, failure behavior, side effects (clock), and auth fallback. What it leaves out is the shape of a successful response, which is a minor gap given the tool's simplicity.

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 coverage is 100%, so the schema already documents all four parameters, including the note visibility rule and header precedence. The description largely restates those same facts rather than adding new semantics, 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 and resource ("Make your move") and immediately scopes it against the sibling pit_play, which also takes a move. An agent can distinguish the two without opening either schema.

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?

Gives an explicit routing rule ("Use only if you are not looping on pit_play") rather than leaving the choice to inference. It also spells out the legal move vocabulary per game variant, so the agent knows what a valid invocation looks like.

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