myersparkathleticzone-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MPAZ_SITE_URL | No | Point at another Athletic Zone school site. | https://www.myersparkathleticzone.com |
| MPAZ_SCHOOL_ID | No | GoFan/PlayOn school id, used to tell your teams from opponents. | 10150 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mpaz_list_teamsA | List this school's athletic teams for a school year, with the team id needed by the schedule, roster and scores tools. Team ids differ per school year — an id from one season fails against another. A past year is answered from the sport pages when the schedule has nothing, which reaches only sports currently in season; the result carries a |
| mpaz_resolve_teamA | Find a team id from a loose name like "varsity football", "girls JV volleyball" or just "field hockey". Use this before mpaz_get_team_schedule / mpaz_get_roster / mpaz_get_scores rather than guessing an id. Returns every candidate when the query is ambiguous. Read-only. |
| mpaz_get_scheduleA | Upcoming events across every team, oldest first. Note this page returns a WINDOW of upcoming events (10 observed), not a whole season — for a team's full season use mpaz_get_team_schedule. Each event's |
| mpaz_get_team_scheduleA | A single team's complete season, oldest first. Requires BOTH the sport slug and the team id — resolve them with mpaz_list_teams or mpaz_resolve_team first. Each event's |
| mpaz_get_scoresA | Completed games with results for a single team: |
| mpaz_get_rosterA | Coaching staff and players for one team. Most teams on this site publish coaches but NOT players, so an empty players list is normal, not an error. Requires the sport slug and team id. Read-only. |
| mpaz_list_newsA | Recent news posts from the athletics site homepage, newest first. Read-only. |
| mpaz_list_videosA | Games with a broadcast link. These are NFHS Network links rather than hosted clips, so |
| mpaz_list_photo_galleriesA | Photo galleries published on the site. Images sit on a public CDN and can be fetched directly, no auth. Read-only. |
| mpaz_healthcheckA | Verify the athletics site is reachable and still serving a parseable RSC payload. Reports the configured site and school id. Read-only. |
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 10 tools
The tools are mostly distinct: get_schedule vs get_team_schedule vs get_scores have clear separation between upcoming window, full season, and completed results, and list_teams vs resolve_team cover listing vs fuzzy lookup. The only mild risk is confusion between the two schedule tools, but the descriptions resolve it clearly.
Almost every tool follows the mpaz_<verb>_<noun> pattern with get/list/resolve verbs, which is easy to predict. mpaz_healthcheck breaks the verb_noun pattern but is a minor outlier and still fits the readable, consistent style.
With 10 tools, the server is well-scoped for a read-only school athletics information API. Each tool covers a distinct content type or lookup need, so none feels redundant or unnecessary.
The set covers team discovery, schedules, rosters, scores, news, galleries, videos, and connectivity checks, which is strong for a read-only domain. Minor gaps exist—content like news, galleries, and videos is list-only without detail retrieval—but agents can work around these without failing on core queries.