Skip to main content
Glama
chrischall

myersparkathleticzone-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get one team's results

mpaz_get_scores
Read-onlyIdempotent

Retrieve completed game results for a team, including home and away scores plus the outcome from the school's perspective. Null scores indicate unknown results, not zero.

Instructions

Completed games with results for a single team: homeScore/awayScore plus teamScore/opponentScore/result from this school's point of view. Each side's score is stored independently upstream, so a half-entered game yields a null score and result: null — a missing score is unknown, never zero. Prefer mpaz_get_team_schedule for upcoming fixtures. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
teamIdYesNumeric team id from mpaz_list_teams / mpaz_resolve_team. Ids differ per school year.
sportSlugYesSport slug, "<gender>-<sport>", e.g. boys-football, girls-volleyball. From mpaz_list_teams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, open-world, and idempotent. The description adds valuable behavioral details beyond these: the null handling (missing score is unknown, never zero) and the timezone distinction (startLocal in school's local time, start in UTC). These disclosures are not implied by annotations and significantly aid correct interpretation of results.

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?

The description is compact and front-loaded: the first sentence states the purpose and core output fields. It efficiently covers null behavior, usage guidance, and timezone nuances in a few sentences without redundancy. Every sentence 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?

Given the tool has no output schema, the description must explain what is returned, and it does: homeScore/awayScore, teamScore/opponentScore/result, plus null semantics and timezone handling. It also provides guidance on parameter selection (past seasons, team id resolution) via the schema. An agent has all necessary context to call the tool correctly and interpret results.

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?

All three parameters are fully described in the schema (coverage 100%), including defaults, patterns, and source (e.g., from mpaz_list_teams). The tool description does not add new parameter semantics; it only reinforces that teamId and sportSlug come from mpaz_list_teams, which the schema already states. Thus, a baseline score of 3 is appropriate since the schema carries the semantic burden.

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 clearly states the tool's function: returning completed games with results for a single team, including specific score fields. It distinguishes from siblings by focusing on a single team's results and explicitly references the alternative for upcoming fixtures. The verb 'get' plus the resource 'results' makes the purpose unambiguous.

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?

The description explicitly directs agents to use mpaz_get_team_schedule for upcoming fixtures, providing a clear condition for choosing an alternative. It also clarifies the null-score semantics for half-entered games, which informs correct interpretation of results. This is concrete, actionable guidance.

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

Deploy Server

Other Tools