Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_team_rankings

Read-only

Get MaxPreps team rankings (national, state, section). Returns a ranked team list for one sport season: national, state (stateCode) or section (sectionId) scope, with the rank, school identity, overall record, rating, strength, movement, team size, last-updated time and total ranked count. The source pages with count and page; teamSize is optional and the source returned the same rankings with and without it.

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": {
      "type": "<type>",
      "allSeasonId": "<allSeasonId>",
      "sportSeasonId": "<sportSeasonId>"
    },
    "name": "maxpreps_team_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional one-based page number. Defaults to 1.
typeYesRequired ranking scope. Values: national, state, section.
countNoOptional page size from 1 to 100. Defaults to 25.
teamSizeNoOptional on-field team size (for example 11 for football, 5 for basketball). The source returned the same rankings with and without it.
sectionIdNoSection id; required when type is section. Discover section ids from maxpreps-team (sectionId) or maxpreps-rankings-groupings.
stateCodeNoState code; required when type is state. Use maxpreps-states for the complete value set.
allSeasonIdYesRequired all-season id from maxpreps-sports.
sportSeasonIdYesRequired sport-season id for the ranked team season.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavior: pagination via count/page and the note that teamSize does not change results. It does not discuss rate limits, error behavior, or empty-result cases, so the added context is modest.

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 scope before the return-field list. The second sentence is dense and repeats the teamSize caveat already in the schema, which is minor waste but not confusing.

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?

An output schema exists, so return values need not be spelled out, yet the description still lists them harmlessly. With 8 parameters, 3 required, and full schema coverage, an agent has everything needed to call it correctly; only cross-tool selection guidance is thin.

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 the schema already documents every parameter including the teamSize no-op note. The description reinforces scope semantics and the teamSize caveat but adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 team rankings') and enumerates the three scopes (national, state, section) plus the returned fields. It is clearly distinguishable from roster/schedule/context siblings, though it never names an alternative rankings tool to contrast against.

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?

Gives concrete prerequisite routing: allSeasonId from maxpreps-sports, stateCode from maxpreps-states, sectionId from maxpreps-team or maxpreps-rankings-groupings. It does not state when to prefer this over other rankings sources or any exclusions, 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.

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