Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_season_navigation

Resolve the season an allSeasonId belongs to and get the site’s own navigation sections—teams, scores, rankings, playoffs, news—with links for that sport season.

Instructions

MaxPreps season navigation tree. Returns the season navigation tree for one allSeasonId: the resolved season name and the site's own navigation sections (Football Home, Teams, Players, States, Scores, Rankings, Stat leaders, Photos, Playoffs, Videos, Record Book, News, Live Streams) with their links. Use it to resolve the season an allSeasonId belongs to and the sport/season pages the site itself links.

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": {
      "allSeasonId": "<allSeasonId>"
    },
    "name": "maxpreps_season_navigation"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season name as the navigation reports it example(Fall)
allSeasonIdYesAll-season id from maxpreps-sports (one per gender+sport) example(22e2b335-334e-4d4d-9f67-a0f716bb1ccd)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does describe the payload shape (resolved season name plus section list with links), which implies a read-only lookup, but it says nothing about error behavior for an invalid allSeasonId, what happens when the optional season name conflicts, or pagination/size characteristics.

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 core action and followed by the enumeration and usage cue. Minor redundancy in repeating 'season navigation tree' twice, and the long parenthetical section list could be tighter, but nothing is wasted.

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?

For a two-parameter, read-only navigation lookup with no output schema, the description compensates well by enumerating what comes back and why to call it. The remaining gap is the semantics of the optional `season` parameter and failure modes on an unknown id.

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%, so both parameters are already documented with examples. The description reinforces the allSeasonId scope ('one allSeasonId') and its role in resolving the season, but adds no meaning for the optional `season` parameter beyond what the schema states.

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 ('Returns the season navigation tree for one allSeasonId') and enumerates the exact contents — resolved season name plus named navigation sections with links. An agent can distinguish this from maxpreps_sports (which supplies the allSeasonId) or maxpreps_scoreboard without opening the 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?

Explicitly frames the use case: 'resolve the season an allSeasonId belongs to and the sport/season pages the site itself links.' That is a clear when-to-use, but there is no when-not guidance or a named alternative for fetching scores/rankings data directly instead of the navigation tree.

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