Royals26
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROYALS26_REQUEST_INTERVAL | No | Request interval in seconds between crawls to the stats site, with jitter. Override with ROYALS26_REQUEST_INTERVAL=5 if you want to be gentler still. | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_teamsA | List all Division 4 teams with group, record and id. |
| standingsA | Current league standings, grouped by division. |
| scheduleC | Fixtures and results. Optionally filter by team, and by whether the game has been played. |
| rosterC | A team's roster: handedness, position, uniform number, season line. |
| team_battingC | Season batting line for every player on a team. |
| team_pitchingB | Season pitching summary for a team's whole staff, with rest days. |
| platoon_splitsC | Each hitter's line against left- and right-handed pitching, computed locally from the play stream. Left-handed pitching is rare in this league so vs-LHP samples are small and flagged accordingly. |
| league_statsB | League-wide season leaderboard from the federation's stats endpoint. section is batting|pitching|fielding. |
| predict_lineupC | Predict a team's batting order 1-9 with per-slot confidence, from their recent lineup cards. |
| probable_pitcherA | Who is likely to start on the mound, from rotation pattern and rest. |
| scout_reportA | Full pre-game scouting report on an opponent: predicted lineup, probable pitchers with stamina curves, running game, count tendencies. Returns markdown. |
| scout_report_dataC | Structured (non-markdown) version of the scouting report. |
| pitcher_profileB | Pitcher profile: season line, stamina by pitch count, first-pitch strike rate, count behaviour, batted-ball mix allowed. |
| hitter_profileC | Hitter profile: season line, approach by count, contact type. |
| running_gameC | A team's steal rate, main basestealers and catcher throwing. |
| count_tendenciesB | How a team's hitters behave by count — swing, whiff and contact rates. |
| small_ballC | Bunt, sacrifice and ground/fly tendencies for a team. |
| suggest_batting_orderB | Suggest a batting order with reasoning. Pass |
| matchupC | Head-to-head history between one batter and one pitcher. |
| playoff_bracketB | The 2026 playoff bracket as recorded in the Google Sheet snapshot. |
| playoff_projectionA | Recompute playoff seeds from the live standings using the 1v5/2v6/3v7/4v8 rule. Useful for week-to-week what-ifs. |
| likely_opponentsC | Who the Royals could face in the playoffs, with scouting priority. |
| sync_leagueA | Refresh the local cache from the BBF site. Slow (about 3 seconds per request, and a first run fetches every box score) and the site's CDN rate-limits, so run it weekly, not before each query. |
| sync_recentA | Fetch only the missing box scores, up to a limit. Use this to work through a backlog gently after a rate-limit block. |
| cache_statusA | What is in the local cache and when it was last refreshed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Most tools target clearly distinct resources or analytical questions, and the descriptions help separate overlapping areas like hitting stats versus scouting. A few pairs—predict_lineup/suggest_batting_order and scout_report/scout_report_data—could cause hesitation, but their descriptions clarify the difference.
Tool names are readable and descriptive, but they mix styles: verb_noun names like list_teams and sync_recent sit alongside bare nouns like standings and roster, and compound names like small_ball or team_pitching. There is no single consistent convention, but the patterns are not chaotic.
At 25 tools the surface is on the heavy side, though the domain—standings, rosters, stats, scouting, and playoffs—is broad enough that most tools serve a distinct purpose. A few duplicative formats and cache-maintenance tools could be trimmed, but the count is not unreasonable.
The toolkit covers the core analytical workflow well: standings, schedules, rosters, batting and pitching stats, player profiles, matchup history, scouting reports, and playoff scenarios. Minor gaps exist such as no per-game box score retrieval or transaction/roster-move tools, but for a read-only analysis server this is solid coverage.