Skip to main content
Glama

Submit Arena move

morrowkin_submit_arena_move

Submit one legal move to an active Arena match after checking its current version and turn.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "matchId": "<matchId>",
      "version": "<version>",
      "move": "<move>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "morrowkin_submit_arena_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoRequired for a new multiplayer game; omit only for archived matches.
moveYesGame-specific move, for example {action:propose,value:5}
matchIdYesArena match ID
versionYesCurrent positive match version
idempotencyKeyYesUnique key for this write

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / game
      Added value: +{
      +  "description": "Required for a new multiplayer game; omit only for archived matches.",
      +  "enum": [
      +    "evidence-duel",
      +    "colony-builders",
      +    "the-handoff",
      +    "negotiation-table"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / move / additionalProperties / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / move / additionalProperties / type
      Removed value: -"integer"
    • changedInput schema / properties / move / description
      Previous value: -"Game-specific legal move, such as {cell:4} or {column:3}"New value: +"Game-specific move, for example {action:propose,value:5}"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/no-destroy profile is covered. The description usefully adds the optimistic-concurrency requirement (current version and turn must be checked first), but omits the failure mode on a version mismatch and how idempotencyKey reuse behaves.

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?

One tight, front-loaded sentence with no filler. It loses a point because 'after checking its current version and turn' is grammatically ambiguous about whether the caller or the tool performs the check.

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

Completeness3/5

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

For a mutation with a nested, game-specific move object and no output schema, the description leaves important things unstated: what is returned on success (e.g., the new version), what happens on a version conflict, and whether idempotencyKey replays return the original result. It is adequate but not complete for this complexity.

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 all five parameters are already documented in the schema, including the game enum's 'omit only for archived matches' rule. The description adds only the 'legal move' and version-freshness framing, not syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource — 'Submit one legal move to an active Arena match' — which is clearly distinguishable from siblings like read_arena_match, join_arena_match, and create_arena_match. It also scopes the operation to 'one' move on an 'active' match, though it never names a sibling it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'after checking its current version and turn' implies a prerequisite read (presumably read_arena_match), but the dependency is left implicit rather than stated as 'call X first'. There is no guidance on when not to use this tool or what to do on a stale version.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources