Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_team_stat_leaders

Retrieve a MaxPreps team season's statistical leaderboard rows, including stat names, values, ranks, leaderboard context, and minimum-games cutoffs—without athlete identity data.

Instructions

MaxPreps team stat leaders. Returns one team season's stat-leader rows: the stat name and header, the stat value, the leader's rank within that stat and the leaderboard context, plus the minimum-games cutoffs the leaderboard applied. Athlete identity (name, photo, positions, class year, ids) is deliberately excluded; this route reports the statistics, not player records.

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": {
      "teamId": "<teamId>",
      "sportSeasonId": "<sportSeasonId>"
    },
    "name": "maxpreps_team_stat_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam id from maxpreps-school-search or maxpreps-team example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)
sportSeasonIdYesSport-season id for that exact team and level example(2286cd80-c46d-4739-8dd1-92a67ca8daa7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the exact return payload shape, that minimum-games cutoffs are included, and that athlete identity fields are deliberately stripped. It stops short of covering pagination, row limits, or failure behavior, which keeps it below a 5.

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?

Three sentences, front-loaded with the purpose followed by return contents and then the scope exclusion; no filler or restatement of the name alone. The middle enumeration of returned fields is slightly dense but each clause carries informational value.

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, fully documented-schema read tool with no output schema and no annotations, the description adequately explains what comes back and what is deliberately omitted. The remaining gap is operational detail (pagination, whether all stats or only leaders are returned), which is minor for this tool's complexity.

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 teamId and sportSeasonId are already documented with examples; the baseline of 3 applies. The description adds only the framing that the season must belong to "one team" at that exact level, without new syntax or format detail beyond the schema.

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?

Names a specific verb and resource ("Returns one team season's stat-leader rows") and enumerates the fields returned: stat name, header, stat value, leader rank, leaderboard context, and minimum-games cutoffs. The explicit exclusion of athlete identity ("this route reports the statistics, not player records") cleanly separates it from roster-oriented siblings such as maxpreps_team_roster_summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase "one team season's stat-leader rows" and the required teamId/sportSeasonId pair, so an agent can infer the scope. However, no alternative tool is named and no when-not conditions or prerequisites (e.g., needing a valid team/season id from maxpreps_team first) are stated.

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