CourtSplit

Rotation plan

rotation_plan

Read-onlyIdempotent

Plan fair player rotations for pickup games: who plays on each court every round and who sits out, balancing games played across the roster. Use when more players show up than court spots. Does not split money; for costs use split_costs or split_series.

Input Schema

Name	Required	Description
`courts`	No	Number of courts in use at once (default 1)
`rounds`	Yes	Number of rounds to schedule, 1-50
`players`	Yes	Unique roster names, at least capacity x courts of them, e.g. ["Asha","Dev","Mira","Sam","Lee","Kai"]
`capacity`	Yes	Players per court: 2 for singles, 4 for doubles, 10 for 5v5 basketball

Output Schema

Name	Required	Description
`note`	Yes	Whether the rotation is perfectly balanced
`format`	Yes	Format label with players per side and courts, e.g. '2v2 on 2 court(s)' for capacity 4 (doubles), '1v1' for capacity 2; odd capacity shows 'N player(s) per court'
`rounds`	Yes	Number of rounds scheduled
`fairness`	Yes	Games-played balance across the roster
`schedule`	Yes	One entry per round

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / properties / format / description

Previous value: -"Format label built from capacity and courts, e.g. '4v4 on 2 court(s)'"New value: +"Format label with players per side and courts, e.g. '2v2 on 2 court(s)' for capacity 4 (doubles), '1v1' for capacity 2; odd capacity shows 'N player(s) per court'"

Changed13 schema fields changedOct 10, 2026

changedInput schema / properties / capacity / description

Previous value: -"Players per court (2 singles, 4 doubles)"New value: +"Players per court: 2 for singles, 4 for doubles, 10 for 5v5 basketball"

addedInput schema / properties / capacity / minimum
```
Added value: +1
```

changedInput schema / properties / capacity / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / courts / description

Previous value: -"Number of courts available for the rotation plan"New value: +"Number of courts in use at once (default 1)"

addedInput schema / properties / courts / minimum
```
Added value: +1
```

changedInput schema / properties / courts / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / players / description

Previous value: -"Roster names"New value: +"Unique roster names, at least capacity x courts of them, e.g. [\"Asha\",\"Dev\",\"Mira\",\"Sam\",\"Lee\",\"Kai\"]"

addedInput schema / properties / players / minItems
```
Added value: +2
```

changedInput schema / properties / rounds / description

Previous value: -"Number of rounds to be scheduled in the rotation plan"New value: +"Number of rounds to schedule, 1-50"

addedInput schema / properties / rounds / maximum
```
Added value: +50
```
addedInput schema / properties / rounds / minimum
```
Added value: +1
```

changedInput schema / properties / rounds / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "fairness": {
+      "description": "Games-played balance across the roster",
+      "properties": {
+        "max_games": {
+          "description": "Most games any player gets",
+          "type": "integer"
+        },
+        "min_games": {
+          "description": "Fewest games any player gets",
+          "type": "integer"
+        },
+        "spread": {
+          "description": "max_games minus min_games",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "min_games",
+        "max_games",
+        "spread"
+      ],
+      "type": "object"
+    },
+    "format": {
+      "description": "Format label built from capacity and courts, e.g. '4v4 on 2 court(s)'",
+      "type": "string"
+    },
+    "note": {
+      "description": "Whether the rotation is perfectly balanced",
+      "type": "string"
+    },
+    "rounds": {
+      "description": "Number of rounds scheduled",
+      "type": "integer"
+    },
+    "schedule": {
+      "description": "One entry per round",
+      "items": {
+        "properties": {
+          "courts": {
+            "description": "Players on each court this round",
+            "items": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "type": "array"
+          },
+          "round": {
+            "description": "Round number starting at 1",
+            "type": "integer"
+          },
+          "sitting": {
+            "description": "Players sitting out this round",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "round",
+          "courts",
+          "sitting"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "format",
+    "rounds",
+    "fairness",
+    "schedule",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "balance": {
-      "description": "Balance of games played by each player",
-      "properties": {
-        "players": {
-          "description": "List of players with their respective games played",
-          "items": {
-            "properties": {
-              "gamesPlayed": {
-                "description": "The number of games the player has played",
-                "type": "number"
-              },
-              "name": {
-                "description": "The player's name",
-                "type": "string"
-              }
-            },
-            "required": [
-              "name",
-              "gamesPlayed"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        }
-      },
-      "required": [
-        "players"
-      ],
-      "type": "object"
-    },
-    "rounds": {
-      "description": "List of rounds with players assigned to each court",
-      "items": {
-        "properties": {
-          "courts": {
-            "description": "List of courts with players assigned to each",
-            "items": {
-              "properties": {
-                "courtNumber": {
-                  "description": "The court number",
-                  "type": "number"
-                },
-                "players": {
-                  "description": "List of players assigned to this court",
-                  "items": {
-                    "type": "string"
-                  },
-                  "type": "array"
-                }
-              },
-              "required": [
-                "courtNumber",
-                "players"
-              ],
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "roundNumber": {
-            "description": "The round number",
-            "type": "number"
-          }
-        },
-        "required": [
-          "roundNumber",
-          "courts"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "rounds",
-    "balance"
-  ],
-  "type": "object"
-}New value: +null

Changed2 schema fields changedOct 6, 2026
- addedInput schema / properties / courts / description
```
Added value: +"Number of courts available for the rotation plan"
```
- addedInput schema / properties / rounds / description
```
Added value: +"Number of rounds to be scheduled in the rotation plan"
```

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "balance": {
+      "description": "Balance of games played by each player",
+      "properties": {
+        "players": {
+          "description": "List of players with their respective games played",
+          "items": {
+            "properties": {
+              "gamesPlayed": {
+                "description": "The number of games the player has played",
+                "type": "number"
+              },
+              "name": {
+                "description": "The player's name",
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "gamesPlayed"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "players"
+      ],
+      "type": "object"
+    },
+    "rounds": {
+      "description": "List of rounds with players assigned to each court",
+      "items": {
+        "properties": {
+          "courts": {
+            "description": "List of courts with players assigned to each",
+            "items": {
+              "properties": {
+                "courtNumber": {
+                  "description": "The court number",
+                  "type": "number"
+                },
+                "players": {
+                  "description": "List of players assigned to this court",
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                }
+              },
+              "required": [
+                "courtNumber",
+                "players"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "roundNumber": {
+            "description": "The round number",
+            "type": "number"
+          }
+        },
+        "required": [
+          "roundNumber",
+          "courts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "rounds",
+    "balance"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered structurally. The description adds genuinely useful behavioral intent beyond that: the fairness objective (balancing games played) and that the plan covers both court assignments and sit-outs. It does not discuss determinism of tie-breaking or how many rounds constrain output, but with annotations and an output schema present the bar is lower.

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

Conciseness5/5

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

Three tight sentences with zero filler: purpose and output first, then the usage trigger, then the explicit boundary against sibling tools. Each sentence earns its place and the most decision-relevant information is front-loaded.

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 annotations covering the safety profile and an output schema covering return shape, the description only needs to convey purpose, trigger, and boundaries — all of which it does. Minor gap: it does not hint that the roster must be at least capacity × courts (a real failure mode), though that constraint is stated in the schema.

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% and every parameter is documented in the schema itself (courts default, rounds 1-50, capacity meaning for singles/doubles/5v5, players roster). The description adds no syntax or format detail beyond that, so the baseline 3 for a fully documented schema is correct.

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 ('Plan fair player rotations for pickup games') and spells out the concrete output semantics: who plays on each court every round, who sits out, and that games played are balanced across the roster. It also explicitly distinguishes itself from the money-oriented siblings by declaring 'Does not split money,' so an agent can separate it from split_costs/split_series without opening any 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 trigger condition ('Use when more players show up than court spots') and names the correct alternatives for the adjacent money domain ('for costs use split_costs or split_series'). That is direct when-to-use plus when-to-use-something-else routing, leaving little to inference.

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

All CourtSplit tools Inspect

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.

Rotation plan

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources