Skip to main content
Glama

LeagueNight

by io.github.everyai-com
OverviewDiscussionsAdmin

Season plan

season_plan
Read-onlyIdempotent

Estimate a season's size and calendar: total round-robin fixtures, games per match day (limited by courts, one slot per day), match days needed, every match-day date from start_date at a fixed interval, and the finish date. Use for "when will the season end?". Do NOT use for pairings (use round_robin_schedule) or one day's timetable (use match_day_plan).

Input Schema

NameRequiredDescriptionDefault
teamsYesTeam names: 2-100 unique, non-empty names (trimmed), e.g. ["Falcons", "Tigers", "Bears"]
courtsYesCourts usable at the same time on each match day, integer 1-12; caps games per match day. E.g. 2
second_legNoIf true, plan a double round-robin (each pair meets twice). Default false
start_dateYesFirst match day, YYYY-MM-DD, e.g. "2026-10-04"
slot_minutesYesLength of one game slot in minutes, integer 10-180 (validated and echoed in the note; each match day is one slot). E.g. 30
days_between_roundsNoDays between consecutive match days, integer 1-60. Default 7 (weekly)

Output Schema

NameRequiredDescriptionDefault
noteYesPlain-English summary of the season plan and assumptions
datesYesEvery match-day date, YYYY-MM-DD, in order
finish_dateYesDate of the last match day, YYYY-MM-DD
games_totalYesTotal fixtures in the season (n(n-1)/2 per leg)
rounds_neededYesNumber of match days needed to play all fixtures
per_team_gamesYesGames each team plays over the season
games_per_roundYesGames played per match day: min(floor(teams/2), courts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed33 schema fields changed
    • changedInput schema / properties / courts / description
      Previous value: -"Courts available per match day (1-12)"New value: +"Courts usable at the same time on each match day, integer 1-12; caps games per match day. 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 / days_between_rounds / description
      Previous value: -"Days between match days, default 7"New value: +"Days between consecutive match days, integer 1-60. Default 7 (weekly)"
    • addedInput schema / properties / days_between_rounds / maximum
      Added value: +60
    • addedInput schema / properties / days_between_rounds / minimum
      Added value: +1
    • changedInput schema / properties / days_between_rounds / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / second_leg / description
      Previous value: -"Plan a double round-robin (each pair meets twice)"New value: +"If true, plan a double round-robin (each pair meets twice). Default false"
    • 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 (validated and echoed in the note; each match day is one slot). E.g. 30"
    • 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_date / description
      Previous value: -"First match day, YYYY-MM-DD"New value: +"First match day, YYYY-MM-DD, e.g. \"2026-10-04\""
    • addedInput schema / properties / start_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedInput schema / properties / teams / description
      Previous value: -"Team names (2 or more, unique)"New value: +"Team names: 2-100 unique, non-empty names (trimmed), e.g. [\"Falcons\", \"Tigers\", \"Bears\"]"
    • addedInput schema / properties / teams / items / description
      Added value: +"Team name, e.g. \"Falcons\""
    • addedInput schema / properties / teams / maxItems
      Added value: +100
    • addedInput schema / properties / teams / minItems
      Added value: +2
    • addedOutput schema / properties / dates
      Added value: +{
+  "description": "Every match-day date, YYYY-MM-DD, in order",
+  "items": {
+    "description": "Match-day date YYYY-MM-DD",
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / estimated_finish_date
      Removed value: -{
-  "description": "The estimated finish date of the season.",
-  "format": "date",
-  "type": "string"
-}
    • addedOutput schema / properties / finish_date
      Added value: +{
+  "description": "Date of the last match day, YYYY-MM-DD",
+  "type": "string"
+}
    • removedOutput schema / properties / games_per_match_day
      Removed value: -{
-  "description": "Number of games scheduled per match day.",
-  "type": "integer"
-}
    • addedOutput schema / properties / games_per_round
      Added value: +{
+  "description": "Games played per match day: min(floor(teams/2), courts)",
+  "type": "integer"
+}
    • addedOutput schema / properties / games_total
      Added value: +{
+  "description": "Total fixtures in the season (n(n-1)/2 per leg)",
+  "type": "integer"
+}
    • removedOutput schema / properties / match_days
      Removed value: -{
-  "description": "Array of match day plans, each with details for that day.",
-  "items": {
-    "properties": {
-      "date": {
-        "description": "The date of the match day.",
-        "format": "date",
-        "type": "string"
-      },
-      "matches": {
-        "items": {
-          "properties": {
-            "team1": {
-              "description": "The name of the first team.",
-              "type": "string"
-            },
-            "team2": {
-              "description": "The name of the second team.",
-              "type": "string"
-            },
-            "time_slot": {
-              "description": "The time slot for the match.",
-              "type": "string"
-            }
-          },
-          "required": [
-            "team1",
-            "team2",
-            "time_slot"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "date",
-      "matches"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / match_days_needed
      Removed value: -{
-  "description": "Total number of match days required to complete the season.",
-  "type": "integer"
-}
    • addedOutput schema / properties / note
      Added value: +{
+  "description": "Plain-English summary of the season plan and assumptions",
+  "type": "string"
+}
    • addedOutput schema / properties / per_team_games
      Added value: +{
+  "description": "Games each team plays over the season",
+  "type": "integer"
+}
    • addedOutput schema / properties / rounds_needed
      Added value: +{
+  "description": "Number of match days needed to play all fixtures",
+  "type": "integer"
+}
    • removedOutput schema / properties / start_date
      Removed value: -{
-  "description": "The start date of the season.",
-  "format": "date",
-  "type": "string"
-}
    • removedOutput schema / properties / total_fixtures
      Removed value: -{
-  "description": "Total number of matches in the season.",
-  "type": "integer"
-}
    • changedOutput schema / required
      Previous value: -[
-  "total_fixtures",
-  "games_per_match_day",
-  "match_days_needed",
-  "start_date",
-  "estimated_finish_date",
-  "match_days"
-]New value: +[
+  "rounds_needed",
+  "games_total",
+  "games_per_round",
+  "per_team_games",
+  "dates",
+  "finish_date",
+  "note"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / match_days / description
      Added value: +"Array of match day plans, each with details for that day."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "estimated_finish_date": {
+      "description": "The estimated finish date of the season.",
+      "format": "date",
+      "type": "string"
+    },
+    "games_per_match_day": {
+      "description": "Number of games scheduled per match day.",
+      "type": "integer"
+    },
+    "match_days": {
+      "items": {
+        "properties": {
+          "date": {
+            "description": "The date of the match day.",
+            "format": "date",
+            "type": "string"
+          },
+          "matches": {
+            "items": {
+              "properties": {
+                "team1": {
+                  "description": "The name of the first team.",
+                  "type": "string"
+                },
+                "team2": {
+                  "description": "The name of the second team.",
+                  "type": "string"
+                },
+                "time_slot": {
+                  "description": "The time slot for the match.",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "team1",
+                "team2",
+                "time_slot"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "date",
+          "matches"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "match_days_needed": {
+      "description": "Total number of match days required to complete the season.",
+      "type": "integer"
+    },
+    "start_date": {
+      "description": "The start date of the season.",
+      "format": "date",
+      "type": "string"
+    },
+    "total_fixtures": {
+      "description": "Total number of matches in the season.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_fixtures",
+    "games_per_match_day",
+    "match_days_needed",
+    "start_date",
+    "estimated_finish_date",
+    "match_days"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description correctly does not restate it. Beyond that it adds genuine behavioral context: the computation is deterministic round-robin sizing, one slot per day, dates stepped at a fixed interval, and slot_minutes is validated and echoed back. It stops short of describing pagination, error conditions, or the note/response structure, so 3 is the right level for a read-only pure-calculation tool.

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, no filler, and the front-loading is deliberate: purpose and outputs first, then the use-case question, then the exclusions. Every clause earns its place.

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?

For a six-parameter, read-only planning tool with a full output schema and complete annotations, nothing an agent needs is missing: purpose, triggering scenario, sibling routing, and the interaction between courts/slots/intervals are all stated, and return values are already covered by the output 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%, so the baseline is 3 and the schema already carries per-parameter bounds, defaults, and formats. The description adds a little interaction semantics (courts caps games per match day; each match day is one slot; dates follow a fixed interval) but introduces no syntax or constraints not already in the schema, so it does not exceed the baseline.

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?

The description opens with a specific verb+resource ("Estimate a season's size and calendar") and enumerates the exact outputs computed: fixtures, games per match day, match days needed, every match-day date, and the finish date. It also explicitly names the sibling tools it is not (round_robin_schedule, match_day_plan), so an agent can distinguish it without inspecting schemas.

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?

It gives a concrete triggering question ("when will the season end?") plus explicit exclusions with named alternatives: pairings go to round_robin_schedule and a single day's timetable to match_day_plan. That is the full when/when-not/alternative trio.

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

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

Resources