LeagueNight

Match day plan

match_day_plan

Read-onlyIdempotent

Compute a one-day timetable: lay an ordered list of games onto parallel courts and fixed-length time slots from a start time, giving each game a court and HH:MM start, plus the end time. Use when you already know the day's games. Do NOT use to decide who plays whom (use round_robin_schedule) or to size a whole season (use season_plan).

Input Schema

Name	Required	Description
`games`	Yes	Games in the order they should be played (non-empty); e.g. one round's fixtures from round_robin_schedule
`courts`	Yes	Number of courts/pitches usable at the same time, integer 1-12, e.g. 2
`start_time`	Yes	First game start, 24h HH:MM, e.g. "09:00" or "18:30"
`slot_minutes`	Yes	Length of one game slot in minutes, integer 10-180, e.g. 40

Output Schema

Name	Required	Description
`note`	Yes	Plain-English summary (slots, courts, after-midnight warning)
`courts`	Yes	Number of courts used in parallel
`end_time`	Yes	Time the last slot finishes, 24h HH:MM (wraps past midnight)
`timeline`	Yes	One entry per game, in input order
`start_time`	Yes	First slot start time, 24h HH:MM (echoed from input)
`slot_minutes`	Yes	Length of each slot in minutes
`total_minutes`	Yes	Total duration from first start to last finish, in minutes

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 10, 2026

changedInput schema / properties / courts / description

Previous value: -"Courts available (1-12)"New value: +"Number of courts/pitches usable at the same time, integer 1-12, e.g. 2"

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

changedInput schema / properties / courts / type

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

changedInput schema / properties / games / description

Previous value: -"Games in the order they should be played"New value: +"Games in the order they should be played (non-empty); e.g. one round's fixtures from round_robin_schedule"

addedInput schema / properties / games / items / properties / away / description
```
Added value: +"Away team name, e.g. \"Tigers\""
```
addedInput schema / properties / games / items / properties / home / description
```
Added value: +"Home team name, e.g. \"Falcons\""
```
addedInput schema / properties / games / minItems
```
Added value: +1
```

changedInput schema / properties / slot_minutes / description

Previous value: -"Minutes per time slot (10-180)"New value: +"Length of one game slot in minutes, integer 10-180, e.g. 40"

addedInput schema / properties / slot_minutes / maximum
```
Added value: +180
```
addedInput schema / properties / slot_minutes / minimum
```
Added value: +10
```
changedInput schema / properties / slot_minutes / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / start_time / description

Previous value: -"First kick-off, 24h HH:MM"New value: +"First game start, 24h HH:MM, e.g. \"09:00\" or \"18:30\""

addedInput schema / properties / start_time / pattern
```
Added value: +"^([01]\\d|2[0-3]):[0-5]\\d$"
```

addedOutput schema / properties / courts

Added value: +{
+  "description": "Number of courts used in parallel",
+  "type": "integer"
+}

addedOutput schema / properties / end_time

Added value: +{
+  "description": "Time the last slot finishes, 24h HH:MM (wraps past midnight)",
+  "type": "string"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "Plain-English summary (slots, courts, after-midnight warning)",
+  "type": "string"
+}

removedOutput schema / properties / schedule

Removed value: -{
-  "description": "List of scheduled games with their respective courts and times.",
-  "items": {
-    "properties": {
-      "away": {
-        "description": "The away team of the game.",
-        "type": "string"
-      },
-      "court": {
-        "description": "The court number where the game is scheduled.",
-        "type": "integer"
-      },
-      "game_index": {
-        "description": "The index of the game in the input list.",
-        "type": "integer"
-      },
-      "home": {
-        "description": "The home team of the game.",
-        "type": "string"
-      },
-      "time": {
-        "description": "The start time of the game in 24h HH:MM format.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "game_index",
-      "home",
-      "away",
-      "court",
-      "time"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / slot_minutes

Added value: +{
+  "description": "Length of each slot in minutes",
+  "type": "integer"
+}

addedOutput schema / properties / start_time

Added value: +{
+  "description": "First slot start time, 24h HH:MM (echoed from input)",
+  "type": "string"
+}

addedOutput schema / properties / timeline

Added value: +{
+  "description": "One entry per game, in input order",
+  "items": {
+    "properties": {
+      "away": {
+        "description": "Away team name",
+        "type": "string"
+      },
+      "court": {
+        "description": "Court number starting at 1",
+        "type": "integer"
+      },
+      "home": {
+        "description": "Home team name",
+        "type": "string"
+      },
+      "time_hhmm": {
+        "description": "Start time 24h HH:MM",
+        "type": "string"
+      }
+    },
+    "required": [
+      "time_hhmm",
+      "court",
+      "home",
+      "away"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / total_minutes

Added value: +{
+  "description": "Total duration from first start to last finish, in minutes",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "schedule"
-]New value: +[
+  "start_time",
+  "end_time",
+  "courts",
+  "slot_minutes",
+  "timeline",
+  "total_minutes",
+  "note"
+]

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "schedule": {
+      "description": "List of scheduled games with their respective courts and times.",
+      "items": {
+        "properties": {
+          "away": {
+            "description": "The away team of the game.",
+            "type": "string"
+          },
+          "court": {
+            "description": "The court number where the game is scheduled.",
+            "type": "integer"
+          },
+          "game_index": {
+            "description": "The index of the game in the input list.",
+            "type": "integer"
+          },
+          "home": {
+            "description": "The home team of the game.",
+            "type": "string"
+          },
+          "time": {
+            "description": "The start time of the game in 24h HH:MM format.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "game_index",
+          "home",
+          "away",
+          "court",
+          "time"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "schedule"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add scheduling semantics, which it does: ordered input, parallel courts, fixed-length slots, and the fields of each emitted entry (court, HH:MM start, end time). It does not disclose what happens to leftover games that exceed the court count in a slot or how slots are numbered, a minor gap.

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 sentences, each earning its place: what it computes, when to use it, and when not to with named alternatives. The core action is front-loaded in the first clause.

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

Completeness5/5

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

With an output schema present the description need not explain return values, and with 100% schema coverage the inputs are fully documented elsewhere. The description closes the remaining gaps: the ordering assumption on input and the routing rules against sibling tools.

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 every parameter (games, courts, slot_minutes, start_time) is already documented in the schema with examples and bounds. The description reinforces the ordering contract of 'games' and the parallel-court semantics of 'courts' but adds no syntax or format detail beyond what the schema provides, 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+resource ('Compute a one-day timetable') and immediately specifies the mechanics: ordered games laid onto parallel courts and fixed-length slots from a start time. It explicitly distinguishes itself from round_robin_schedule and season_plan by naming the sibling it is not, so an agent can route without opening a 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 positive condition ('Use when you already know the day's games') plus two explicit exclusions with the correct alternative named for each ('use round_robin_schedule', 'use season_plan'). Nothing about when to pick this tool is left to inference.

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

All LeagueNight 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.