Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_team

Retrieves a MaxPreps team-season record using team and season IDs, including school, sport, league, section, division, association, and canonical URL details for scoreboard and ranking lookups.

Instructions

MaxPreps team-season record. Returns one team-season record by teamId and sportSeasonId: school identity and address, season/level/gender/sport, league, section and state division (with their ids), governing association and the team's canonical URL. The returned sectionId, leagueId, stateDivisionId and associationId are the identifiers maxpreps-scoreboard and maxpreps-team-rankings accept for their non-state contexts.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam id from maxpreps-school-search or maxpreps-school-zip-search 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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does well on output shape (no output schema exists, so listing the returned fields is valuable) and reveals a cross-tool contract for the returned ids, but it says nothing about failure modes for bad ids, whether the call is a pure read, or rate/limit behavior.

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 purpose and entity scope before the downstream-identifier note. Dense but every clause carries information; the field enumeration is long yet justified by the absence of an output schema.

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 lookup with no output schema, the definition covers what is needed: what record is fetched, what comes back, and how the returned ids feed other tools. The remaining gap is behavior on invalid or mismatched teamId/sportSeasonId pairs, which an agent would have to discover empirically.

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 are documented with example UUIDs, so the baseline of 3 applies. The description only restates that the record is selected 'by teamId and sportSeasonId' and adds no format, sourcing, or level-coupling detail beyond what the schema already says.

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?

Names a concrete resource and operation: a single MaxPreps team-season record keyed by teamId and sportSeasonId, and enumerates the returned fields (school identity/address, season/level/gender/sport, league, section, state division, association, canonical URL). This distinguishes it in practice from siblings like maxpreps_team_schedule or maxpreps_team_roster_summary, though it never names those siblings explicitly.

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 clear context for use by stating exactly which identifiers the tool consumes and, more usefully, which downstream tools (maxpreps-scoreboard and maxpreps-team-rankings) can consume the returned sectionId, leagueId, stateDivisionId and associationId in non-state contexts. There are no explicit when-not conditions or comparisons to the other team-scoped siblings, which keeps it short of 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