Crawlora MCP

maxpreps_team_roster_summary

Read-only

Get MaxPreps team roster counts. Returns one team season's roster counts only: whether the team has a team photo, the athlete count, how many athletes have a photo or jersey number, and the Hudl athlete count. Coach names and staff records are personal data and are excluded; use this route for roster size, not for 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_roster_summary"
  }
}

Input Schema

Name	Required	Description	Default
`teamId`	Yes	Required team id from maxpreps-school-search or maxpreps-team.
`sportSeasonId`	Yes	Required sport-season id for that exact team and level.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.1/5.0

Behavior4/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 profile is covered. The description adds real behavioral context beyond that: the strict single-team-season scope, the enumerated metric set, and the deliberate exclusion of coach/staff personal data, which signals a privacy-driven omission rather than missing data. It does not discuss rate limits or error behavior, but that is not essential for a read-only aggregate lookup.

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 tight sentences, front-loaded with the core action and then the scope constraint and exclusion. There is mild redundancy between 'roster counts' and 'roster counts only', but no filler or tangential content.

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, the return shape need not be explained, yet the description still summarizes the metrics and flags the personal-data exclusion — the two things an agent most needs. Parameters are fully documented in the schema, so the remaining gap is only the unnamed fallback tool for player-level data.

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 carry their own descriptions ('team id from maxpreps-school-search or maxpreps-team', 'sport-season id for that exact team and level'). The description reinforces the 'one team season' scoping but adds no syntax, format, or edge-case detail beyond what the schema already states, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('Get MaxPreps team roster counts') and immediately narrows the scope to 'one team season's roster counts only'. It enumerates the exact fields returned (team photo flag, athlete count, photo/jersey-number counts, Hudl count), so an agent can distinguish it from player-record tools like espn_team_roster or maxpreps_team without inspecting a 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?

It gives an explicit when-to-use ('use this route for roster size') and an explicit when-not ('not for player records'), plus the caveat that coach names and staff records are excluded. The only gap is that it does not name the specific sibling tool to use for player records, leaving the agent to search for it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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.