Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_team_context

Retrieve focused MaxPreps team-season context using team and sport-season IDs to get identity, records, rankings, standings, market areas, and affiliations.

Instructions

MaxPreps team page context. Returns the focused team page context for one team season: the team identity (same shape as maxpreps-team), every school sport-season, the sport's own vocabulary (contest/athlete aliases, period alias, overtime alias), the state record, the team's ranking summaries for the current and last season, its overall and league standings, its designated market areas, its association affiliations and its content-availability flags. Site chrome, partner/commerce blocks, team photo and internal settings are excluded.

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

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.7/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 burden and does a decent job: it discloses the exact payload contents and, unusually, what is deliberately excluded (site chrome, partner/commerce blocks, team photo, internal settings), which prevents an agent from hunting for data that will never appear. It stops short of noting payload size, latency, or that the operation is a pure read with no side effects.

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, purpose front-loaded, and the long enumeration is justified because there is no output schema and it is the only specification of return contents. The nested list is dense but every item maps to a real payload section rather than filler.

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 rich aggregate tool with no output schema, the description substitutes well by naming every returned section and every excluded section, so an agent can decide whether one call covers its need. The remaining gap is routing guidance against the numerous narrower maxpreps_team_* siblings, which the description leaves unaddressed.

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%: both teamId and sportSeasonId already document their provenance (maxpreps-school-search / maxpreps-team) and the level-specific constraint. The description adds no additional parameter meaning, 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 uses a specific verb ('Returns') and resource ('focused team page context for one team season'), then enumerates the payload components (identity, sport-seasons, vocabulary aliases, records, rankings, standings, DMAs, affiliations, availability flags). It partially differentiates from siblings by noting the identity is 'same shape as maxpreps-team' and that this is the aggregate page context, but it never explicitly contrasts the scope with maxpreps_team or maxpreps_team_rankings.

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 only implied: the word 'context' plus the long inclusion list signal a one-call broad snapshot rather than a narrow query. There is no explicit when-to-use statement, no 'prefer this over calling X and Y separately', and no stated prerequisites or exclusions relative to the many maxpreps_team_* siblings.

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