Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_rankings_groupings

Retrieve a state season’s ranking groupings—divisions, associations, market areas, and naming aliases with IDs and URLs—to discover the IDs needed for scoreboard and team-ranking queries.

Instructions

MaxPreps ranking groupings for a state season. Returns one state season's ranking groupings: the league/section/division/athlete naming aliases, the state divisions, the associations and the designated market areas, each with its id and canonical rankings/scoreboard URLs. This is the discovery surface for the sectionId, stateDivisionId, associationId and dmaId values maxpreps-scoreboard and maxpreps-team-rankings accept.

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": {
      "stateCode": "<stateCode>",
      "sportSeasonId": "<sportSeasonId>"
    },
    "name": "maxpreps_rankings_groupings"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateCodeYesState code from maxpreps-states
sportSeasonIdYesSport-season id for the ranked team season example(2286cd80-c46d-4739-8dd1-92a67ca8daa7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: this is a read-only discovery/lookup surface and the response shape (four groupings with ids and URLs) is described even though no output schema exists. It omits permissions, rate limits, and what happens for an invalid season id or a state with no associations, leaving some behavioral gaps.

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 the purpose and followed by the payload contents and the integration hint. Every clause carries information; the enumeration of returned groupings directly serves tool selection and result interpretation.

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?

With no output schema and no annotations, the description compensates by describing the return contents in detail and explaining what the returned ids are used for downstream. For a simple two-parameter lookup tool, nothing an agent needs in order to call and use the result is missing.

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% and both parameters are documented in-schema (stateCode is tied to maxpreps-states, sportSeasonId carries an example). The description adds no parameter-level detail beyond the framing 'for a state season', so it does not exceed the schema's contribution. Baseline 3 is appropriate.

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+resource ('MaxPreps ranking groupings for a state season') and then enumerates exactly what the payload contains: league/section/division/athlete naming aliases, state divisions, associations, DMAs, each with id and canonical URLs. This is concrete enough for an agent to distinguish it from sibling ranking/scoreboard tools that consume these IDs rather than produce them.

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 positions the tool in a workflow: it is 'the discovery surface for the sectionId, stateDivisionId, associationId and dmaId values maxpreps-scoreboard and maxpreps-team-rankings accept.' That gives a clear when-to-use and names the downstream tools that benefit. It stops short of an explicit 'do not call this to get actual rankings' exclusion, which would have earned a 5.

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