Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_school_seasons

Retrieve every sport-season entry a school publishes—one row per team, level and year—with sportSeasonId, season details, and canonical team URL to find IDs for team data queries.

Instructions

MaxPreps school sport seasons. Returns every sport-season entry one school publishes: one row per team at each level and year, with the sportSeasonId, allSeasonId, gender, sport, level, teamLevel, season and year, and the canonical team URL. This is the discovery surface for the sportSeasonId values that maxpreps-team, maxpreps-team-schedule, maxpreps-team-stat-leaders, maxpreps-team-roster-summary, maxpreps-team-next-contest and maxpreps-team-context require.

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": {
      "schoolId": "<schoolId>"
    },
    "name": "maxpreps_school_seasons"
  }
}

Input Schema

NameRequiredDescriptionDefault
schoolIdYesSchool id from maxpreps-school-search or maxpreps-school-zip-search example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/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 delivers: it implies a read-only enumeration, discloses the row cardinality and field set (sportSeasonId, allSeasonId, gender, sport, level, teamLevel, season, year, canonical team URL), and notes the canonical URL is included. It stops short of pagination or result-size behavior for a school that publishes many teams, which is the remaining gap.

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?

Two sentences, front-loaded with what is returned and the row grain, then the downstream purpose. The field list is dense but functional, and no sentence is filler.

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 enumerating the returned fields and row shape. With no annotations, it implicitly conveys read-only enumeration. Only pagination/volume behavior is unaddressed, a small gap for a single-parameter listing tool.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents schoolId and its provenance. The description only implies a singular school scope ('one school publishes') and adds no format or validation detail beyond the schema — baseline 3.

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 uses a specific verb ('Returns') plus a precisely scoped resource: 'every sport-season entry one school publishes', and clarifies the row grain ('one row per team at each level and year'). This distinguishes it from maxpreps_school and maxpreps_team without requiring the schema to be opened.

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?

It explicitly states the role: 'the discovery surface for the sportSeasonId values' that six named sibling tools require. That tells the agent both when to call this tool and which tools depend on its output, which is the key routing decision here.

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