Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_team_schedule

Fetch a MaxPreps team's full season schedule with per-game scores, contest status, site details, and canonical URLs for schedule tracking and analysis.

Instructions

MaxPreps team schedule and results. Returns one team season's full schedule with results: each contest's date, site, state, per-team scores (b1..b30), result, home/away type, forfeit/TBA flags, contest state (Pregame, ContestInProgress, Boxscore, ScoreNotReported) and the derived fields the site renders (title, contest alias, canonical URL, overtime, tournament and bracket identity).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "teamId": "<teamId>",
      "sportSeasonId": "<sportSeasonId>"
    },
    "name": "maxpreps_team_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam id from maxpreps-school-search or maxpreps-team example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)
sportSeasonIdYesSport-season id for that exact team and level example(2286cd80-c46d-4739-8dd1-92a67ca8daa7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does substantial work: it enumerates what comes back, including contest state values (Pregame, ContestInProgress, Boxscore, ScoreNotReported), forfeit/TBA flags, and derived rendering fields. It does not state that the call is read-only, nor mention result-set size, pagination, or rate limits for a full season of contests.

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?

The purpose statement is front-loaded in the first clause, and the remainder is an inventory of returned fields, which is justified because no output schema exists. The enumeration is dense and includes low-value detail like the b1..b30 score-key range, which borders on schema-dumping rather than description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Two required parameters, no nested objects, and no output schema, so the description must explain the return payload, which it does thoroughly, down to contest states and derived fields. The remaining gap is operational rather than semantic: nothing about volume, whether in-progress seasons are covered, or what an empty schedule looks like.

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 coverage is 100% and both parameters carry descriptions with concrete example ids, so the baseline applies. The description adds only the framing that the two ids must refer to the same team and level ('one team season's'), and offers no additional constraint on id format or how to obtain the sportSeasonId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieves one MaxPreps team season's full schedule with results. It is clearly distinguishable from a single-contest or school-level tool by the phrase 'one team season's full schedule', though it never names a sibling such as maxpreps_team_next_contest or maxpreps_school_contests to make the boundary explicit.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for a whole-season team schedule, and the required teamId/sportSeasonId pair signals that a team must already be resolved. There is no when-to-use/when-not guidance, no prerequisite chain (e.g. resolve ids via maxpreps_school_search or maxpreps_team first), and no pointer to the narrower next-contest tool for upcoming games only.

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