Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

maxpreps_scoreboard

Retrieve MaxPreps scoreboard contest IDs by date for a selected context, sport, and level, including canonical URLs and date-grouped IDs to discover scheduled games.

Instructions

MaxPreps scoreboard contest ids by date. Returns the scoreboard for one context (National, State, Section, StateDivision, Association, League or DMA) and one genderSport and level: the yesterday/today/tomorrow scoreboard canonical URLs and the contest ids grouped by date. Use the ids to discover which games exist on a date; this route returns the id index, not the contest detail.

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": {
      "context": "<context>",
      "genderSport": "<genderSport>",
      "level": "<level>"
    },
    "name": "maxpreps_scoreboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoContext identifier: state code for National (use NN) and State, otherwise a section/state-division/association/league/DMA id example(FL)
levelYesTeam level: Varsity, JV or Freshman
contextYesScoreboard context: National, State, Section, StateDivision, Association, League or DMA; see maxpreps-request-enums for the id kind each context needs
genderSportYesGender+sport value from maxpreps-sports in lowercase, for example boys,football. Case-insensitive; see maxpreps-sports for all 64 values example(boys,football)
excludeTbaDateNoExclude contests whose date is still TBA
nationalTeamCountNoNumber of nationally ranked teams to include for a National context scoreboard example(10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/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 does reasonably well: it discloses the exact return payload (yesterday/today/tomorrow canonical URLs plus contest ids grouped by date) and the critical limitation that it is an index rather than game detail. It says nothing about multi-day behavior beyond yesterday/today/tomorrow, error handling for invalid context/id combinations, or whether results are cached.

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?

Two sentences, front-loaded with the identity and scope, then the use case and limitation. Dense but each clause earns its place; the phrasing around 'the yesterday/today/tomorrow scoreboard canonical URLs' is slightly awkward but not wasteful.

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?

With no output schema, the description correctly compensates by describing the returned URLs and grouped contest ids. For a six-parameter read lookup with 100% schema coverage, the remaining gap is minor behavioral detail (id/context interaction outside National, multi-day scope) rather than anything blocking a correct call.

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% and both enums are documented, so the schema does the heavy lifting. The description reinforces the single-context, single-genderSport, single-level tuple constraint, which is modest added meaning, but it adds no format or combination rules beyond what the schema already states.

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?

The description names a specific resource and verb ('MaxPreps scoreboard contest ids by date') and scopes it to exactly one context, one genderSport and one level. It also pre-empts confusion with a detail-level tool by stating 'this route returns the id index, not the contest detail.' It stops short of naming which sibling to use for contest detail, so 4 rather than 5.

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?

It gives an explicit use case: 'Use the ids to discover which games exist on a date,' and explicitly rules out the adjacent task by noting it does not return contest detail. No explicit when-not conditions or named alternatives are given, which keeps it below 5.

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