Skip to main content
Glama
myersparkathleticzone-mcp

myersparkathleticzone-mcp

by chrischall

Get the all-school schedule

mpaz_get_schedule
Read-onlyIdempotent

Retrieve upcoming Myers Park athletic events across all teams, sorted oldest first, to quickly see what games are coming up. Use it for a short schedule window; for a team's full season, use the team schedule tool.

Instructions

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 startLocal is the local time at the school (in timeZone, e.g. America/New_York) — quote it as-is; start is the same moment in true UTC. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mpaz_get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"full" (default) returns the structured result; "brief" returns one line per item: title — <ISO date or "no date"> — <status>.
yearNoSchool year, e.g. "2026-2027". Defaults to the current one. Past seasons often work; resolve that year's team id with mpaz_list_teams first and read its `coverage` note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns the structured result; \"brief\" returns one line per item: title — <ISO date or \"no date\"> — <status>.",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the readOnly/idempotent annotations by disclosing the windowed result size (10 observed) and the timezone semantics of startLocal vs start. That is exactly the context an agent needs to avoid misreporting a partial list as a full season.

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

Conciseness4/5

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

Front-loaded with scope and ordering, then caveats and timezone guidance in short clauses. Dense with backticked field names but every sentence carries useful information.

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 no output schema, the description supplies the return-value semantics (startLocal, start, timeZone) and the result-size limitation. Nothing essential for correct invocation or interpretation is missing.

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 both view and year are already documented in the schema. The description adds no parameter specifics of its own, which is the baseline case when the schema does the work.

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 ('Upcoming events across every team') plus ordering ('oldest first'), and explicitly distinguishes itself from the season-scoped sibling mpaz_get_team_schedule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly names the alternative tool and the condition that selects it ('for a team's full season use mpaz_get_team_schedule'), and hints at mpaz_list_teams for past-year coverage. Missing only an explicit statement of when this windowed view should be preferred over per-team calls.

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