Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

maxpreps_sports

Retrieves the complete MaxPreps gender-and-sport taxonomy grouped by Boys, Co-ed, and Girls, returning allSeasonId, display name, URL, and canonical tokens for discovering valid sport filters.

Instructions

MaxPreps gender and sport taxonomy. Returns the complete MaxPreps gender/sport taxonomy grouped by Boys, Co-ed and Girls: 64 gender+sport entries covering 40 distinct sports. Each entry carries its own allSeasonId, display name, public URL, canonical genderSport token, schedule model and stat model. This is the discovery surface for the genderSport enum and the allSeasonId values the other routes accept.

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": "maxpreps_sports"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the return shape (64 entries grouped into Boys/Co-ed/Girls), the per-entry fields (allSeasonId, display name, public URL, genderSport token, schedule model, stat model), and the tool's role as a static discovery surface. It does not explicitly state read-only/no-side-effects or explain what 'schedule model' and 'stat model' mean, leaving minor behavioral gaps for a zero-parameter lookup.

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?

Three sentences, front-loaded with the resource and scope, then concrete counts and the per-entry payload, then the discovery-surface purpose. Every sentence adds information; none restates the tool name or wastes space.

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?

There is no output schema, so the description must describe return values, and it does: grouping, entry count, sport count and the per-entry field list. Completeness is slightly reduced because field meanings like 'schedule model' and 'stat model' are named but not explained, and no example token values are shown, though neither blocks correct invocation of a zero-parameter taxonomy tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no input semantics to clarify and the dimension defaults to the baseline. The description instead spends its words on output semantics, which is the useful counterpart but does not change the parameter score.

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 gives a specific verb and resource ('Returns the complete MaxPreps gender/sport taxonomy') and immediately narrows scope: grouped by Boys, Co-ed and Girls, 64 entries over 40 sports. It also frames the tool's role as the discovery surface for the genderSport enum and allSeasonId values consumed by other routes, which lets an agent place it correctly among the MaxPreps siblings without opening any schema.

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?

The closing sentence gives clear usage context: call this to discover genderSport tokens and allSeasonId values before invoking the other MaxPreps routes. It does not state exclusions or name a specific alternative (e.g., how it differs from maxpreps_request_enums or maxpreps_tournament_sports), so it stops short of full when/when-not guidance.

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

Deploy Server