arcade_make_moveApply one validated move at the current revision. Moves are persisted and cannot be undone. If the revision is stale, read the game state again before retrying.
| Name | Required | Description | Default |
|---|---|---|---|
| move | Yes | ||
| revision | Yes | ||
| sessionId | Yes | ||
| sessionToken | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / move / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "type": {
- "enum": [
- "distance",
- "bearing",
- "pulse",
- "locate"
- ],
- "type": "string"
- },
- "x": {
- "maximum": 7,
- "minimum": 0,
- "type": "integer"
- },
- "y": {
- "maximum": 7,
- "minimum": 0,
- "type": "integer"
- }
- },
- "required": [
- "type",
- "x",
- "y"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "cell": {
- "maximum": 15,
- "minimum": 0,
- "type": "integer"
- },
- "type": {
- "const": "rotate",
- "type": "string"
- }
- },
- "required": [
- "type",
- "cell"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "actions": {
- "items": {
- "enum": [
- "north",
- "east",
- "south",
- "west",
- "fire",
- "shield",
- "capture",
- "wait"
- ],
- "type": "string"
- },
- "maxItems": 3,
- "minItems": 3,
- "type": "array"
- },
- "type": {
- "const": "program",
- "type": "string"
- }
- },
- "required": [
- "type",
- "actions"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "direction": {
- "enum": [
- "north",
- "east",
- "south",
- "west"
- ],
- "type": "string"
- },
- "type": {
- "const": "walk",
- "type": "string"
- }
- },
- "required": [
- "type",
- "direction"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "cell": {
- "maximum": 24,
- "minimum": 0,
- "type": "integer"
- },
- "type": {
- "const": "press",
- "type": "string"
- }
- },
- "required": [
- "type",
- "cell"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "direction": {
- "enum": [
- "north",
- "east",
- "south",
- "west"
- ],
- "type": "string"
- },
- "type": {
- "const": "sail",
- "type": "string"
- }
- },
- "required": [
- "type",
- "direction"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "type": {
- "const": "wait",
- "type": "string"
- }
- },
- "required": [
- "type"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "type": {
+ "enum": [
+ "distance",
+ "bearing",
+ "pulse",
+ "locate"
+ ],
+ "type": "string"
+ },
+ "x": {
+ "maximum": 7,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "y": {
+ "maximum": 7,
+ "minimum": 0,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "type",
+ "x",
+ "y"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "cell": {
+ "maximum": 15,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "type": {
+ "const": "rotate",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "cell"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "actions": {
+ "items": {
+ "enum": [
+ "north",
+ "east",
+ "south",
+ "west",
+ "fire",
+ "shield",
+ "capture",
+ "wait"
+ ],
+ "type": "string"
+ },
+ "maxItems": 3,
+ "minItems": 3,
+ "type": "array"
+ },
+ "type": {
+ "const": "program",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "actions"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "direction": {
+ "enum": [
+ "north",
+ "east",
+ "south",
+ "west"
+ ],
+ "type": "string"
+ },
+ "type": {
+ "const": "walk",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "direction"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "cell": {
+ "maximum": 24,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "type": {
+ "const": "press",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "cell"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "direction": {
+ "enum": [
+ "north",
+ "east",
+ "south",
+ "west"
+ ],
+ "type": "string"
+ },
+ "type": {
+ "const": "sail",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "direction"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "direction": {
+ "enum": [
+ "clockwise",
+ "counterclockwise"
+ ],
+ "type": "string"
+ },
+ "ring": {
+ "maximum": 2,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "type": {
+ "const": "turn",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "ring",
+ "direction"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "type": {
+ "const": "wait",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds important behavioral context beyond annotations: moves are persisted, cannot be undone, and stale revisions require re-reading state before retrying. It does not cover error handling for invalid moves or authentication details, but the key mutation and concurrency behavior is well disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three tightly written sentences with no filler. The critical constraint, applying a move at the current revision, is front-loaded, and each subsequent sentence adds actionable behavioral information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the most important behavioral facts for a mutation tool: persistence, irreversibility, and stale-revision handling. However, with no output schema and no parameter descriptions in the schema, it leaves the complex move format and session parameters to be inferred from the raw schema. It is adequate but has clear gaps for a tool with this level of input complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and there are four required parameters, including a complex polymorphic move object. The description only clarifies that revision must be current and that stale revisions require re-reading state; it does not explain sessionId, sessionToken, or the move structure and validation rules. This is insufficient compensation for the schema coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Apply one validated move at the current revision.' This clearly distinguishes making a move from sibling operations like reading game state or starting a game. However, it does not explicitly name or compare itself against any sibling tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear context for use: the move must be applied at the current revision, and if the revision is stale the agent should read the game state again before retrying. This provides a concrete recovery path without explicitly naming the sibling tool for reading state. No explicit when-not-to-use guidance is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.