Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_team

Read-only

Get 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
teamIdYesRequired team id; for a school's varsity team this equals the school id from maxpreps-school-search.
sportSeasonIdYesRequired sport-season id for that exact team and level; discover it from maxpreps-school-search teams or maxpreps-team.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, so the bar is lower. The description still adds real behavioral value: it discloses that exactly one record comes back and, more importantly, that the embedded section/league/state-division/association ids are the accepted inputs for non-state contexts of maxpreps-scoreboard and maxpreps-team-rankings, which an agent could not infer from annotations alone.

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 verb and cardinality. The second sentence is a long comma-separated field inventory that partly duplicates the existing output schema, which keeps it from a 5, but nothing is truly extraneous.

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 description need not explain return values, and annotations carry the safety profile. It covers purpose, key inputs, returned identity and cross-tool id reuse; only the not-found/error behavior and the contrast with maxpreps_team_context are left unstated.

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 substantive descriptions, including how teamId relates to the school id from maxpreps-school-search and how to discover sportSeasonId. The description adds nothing beyond the schema for parameters, so the baseline 3 applies.

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?

The description opens with a specific verb and resource ('Get MaxPreps team-season record') and immediately narrows scope to a single record keyed by teamId and sportSeasonId, then enumerates the payload (school identity, season/level/gender/sport, league, section, state division, association, canonical URL). That is enough for an agent to separate it from siblings like maxpreps_team_rankings or maxpreps_team_roster_summary, though it never explicitly states the contrast.

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 cardinality ('Returns one team-season record') and by the note that the returned sectionId, leagueId, stateDivisionId and associationId feed maxpreps-scoreboard and maxpreps-team-rankings. That is downstream chaining guidance rather than when-to-use-this-vs-an-alternative guidance; there is no statement about when not to use it or how it differs from maxpreps_team_context.

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

All Crawlora MCP toolsInspect
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.

Resources