Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_season_navigation

Read-only

Get 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 such as Fall, Winter or Spring, as the season navigation reports it.
allSeasonIdYesRequired all-season id from maxpreps-sports; one per gender+sport (for example 22e2b335-334e-4d4d-9f67-a0f716bb1ccd).

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-web profile is covered. The description adds useful framing that the tree is the site's own navigation plus a resolved season name, but says nothing about failure behavior for an unknown or stale allSeasonId, or about link volatility.

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, purpose front-loaded, with the parenthetical section list doing real work in setting expectations for the result. The enumeration is somewhat long but earns its place by making the return shape concrete.

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 an output schema present and annotations covering the safety profile, the description only needs to establish purpose, input scoping, and intended use — all of which it does. Minor gap: no indication of what happens when the allSeasonId doesn't resolve to a season.

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 coverage is 100%, so the schema already documents both parameters including the allSeasonId format and the origin from maxpreps-sports; baseline 3 applies. The description reinforces the single-id scoping ('for one allSeasonId') but does not mention the optional `season` parameter or how it interacts with the resolved season name.

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 season navigation tree') and immediately scopes it to 'one allSeasonId', which distinguishes it from sibling navigation tools and from maxpreps_sports / maxpreps_school_seasons. The enumerated section list makes the payload concrete rather than abstract.

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 second sentence gives a clear use case: 'resolve the season an allSeasonId belongs to' and discover 'the sport/season pages the site itself links'. It lacks explicit when-not guidance or a named alternative (e.g., when to prefer maxpreps_sports for id lookup), so it stops short of a 5.

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