Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_team_roster_summary

Retrieve one MaxPreps team season's roster counts, including athlete totals, photo and jersey-number coverage, team photo presence, and Hudl athlete count. Use it for roster size, not player records.

Instructions

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

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

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does add real behavioral context: aggregate counts only, no coach or staff personal data, and a warning that this is not a player-detail route. It stops short of stating read-only semantics explicitly, pagination, or error behavior, but the privacy scoping and output shape disclosure are substantive for a read-only count endpoint.

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?

Three tight sentences with the core subject front-loaded in the first clause and no redundant restatement of the name or title. Every sentence contributes either scope, output detail, or the exclusion.

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?

Two required parameters are fully documented in the schema, and the description compensates for the absent output schema by enumerating what the counts contain. It lacks only minor operational detail such as failure modes when teamId and sportSeasonId do not correspond.

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% and both parameters carry format examples plus their source tool, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which matches the baseline 3.

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 states a specific resource and enumerates exactly what is returned: team-photo presence, athlete count, athletes with photo or jersey number, and Hudl athlete count. It also explicitly distinguishes itself from player-record routes, so an agent can tell it apart from sibling roster tools without opening 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 both a positive use case ("use this route for roster size") and an exclusion ("not for player records"), which is more than most definitions offer. It stops short of naming a concrete alternative route for player records, so the agent must infer the redirect target from sibling names.

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