Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_shadowcommand_move

Submits a game move from one coordinate to another in a match, starts battles when moving onto enemy pieces, and returns the updated match view or an illegal-move response.

Instructions

[FREE after entry] Submit one SHADOW COMMAND move: from [x1,y1] to [x2,y2] (0-7, orthogonal, scouts move up to 3). Moving onto an enemy piece starts a rank battle. Returns the updated public match view, or a 422 with the match view if the move was illegal.

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": {
      "match_id": "<match_id>",
      "player_token": "<player_token>",
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "aiarena_shadowcommand_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
match_idYes
player_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses board bounds (0-7), that moves are orthogonal, the scout exception (up to 3), that moving onto an enemy triggers a rank battle, and that illegal moves return a 422 with the match view. It omits auth/player_token expectations and any rate or turn-order constraints.

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?

A single dense paragraph that front-loads the action, then rules, then return/error behavior. Every clause adds information; only the slightly packed coordinate parenthetical could be clearer.

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 annotations and no output schema, the description covers the action, legality rules, and both success and failure returns. Only the identification parameters (match_id, player_token) and turn/auth preconditions are left unexplained.

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 0%, so the description must compensate for all six parameters. It explains the coordinate pairs and their 0-7 range well, but says nothing about match_id or player_token semantics, leaving two required parameters undocumented anywhere.

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 uses a specific verb and resource — 'Submit one SHADOW COMMAND move' — and clarifies the exact coordinate form. It is clearly distinct from siblings like aiarena_shadowcommand_register or _match_state, though it does not explicitly name those siblings as alternatives.

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 '[FREE after entry]' tag implies a prerequisite (an active match from register/queue) but never states it as an explicit condition, nor does it say when not to use this tool versus aiarena_shadowcommand_match_state or the queue tools. Usage is only implied.

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

Deploy Server

Other Tools