Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_school_seasons

Read-only

Get 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
schoolIdYesRequired school id from maxpreps-school-search or maxpreps-school-zip-search.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value by disclosing result granularity ("one row per team at each level and year") and the presence of a canonical team URL, which tells the agent the response is flat and multi-row rather than a single summary object. It does not describe ordering, result size, or pagination behavior for a school with many teams, which is the main 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then the return shape, then the downstream dependency — a logical order with no filler. The field enumeration and six-tool list are long sentences, and the field list partially duplicates what the output schema already provides, which keeps it just short of ideal.

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?

For a single-parameter read tool with a full output schema and safe-read annotations, everything an agent needs to decide and call is present: when to use it, what ID to pass and where to get it, and what the rows mean. The inline field description is redundant with the output schema but confirms rather than omits.

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?

Only one parameter (schoolId) at 100% schema description coverage, and the schema already states it is required and where to obtain it (maxpreps-school-search / maxpreps-school-zip-search). The description adds only the implicit notion that the ID selects "one school," so the baseline of 3 applies when the schema carries the semantics.

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?

States a specific verb and resource ("Get MaxPreps school sport seasons") and immediately specifies the exact shape of what comes back: one row per team per level and year, with a concrete field list including sportSeasonId and the canonical team URL. It is clearly distinguishable from sibling season tools by being school-scoped rather than tournament- or league-scoped.

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?

Explicitly positions the tool as "the discovery surface for the sportSeasonId values" and names the six consumer tools (maxpreps-team, -team-schedule, -team-stat-leaders, -team-roster-summary, -team-next-contest, -team-context) that require those IDs. This gives the agent an unambiguous call order: enumerate here first, then call the team tools. No explicit exclusion list, but the dependency routing is precise enough to govern selection.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources