Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_team_next_contest

Retrieve a MaxPreps team season's next contest with date, site, teams, scores, state, canonical URL, TBA flags, and Hudl linkage; media and commerce stream fields are excluded.

Instructions

MaxPreps team next contest. Returns one team season's next-contest box: the contest (date, site, teams, scores, home/away type, contest state) with the same contest shape as maxpreps-team-schedule, the derived fields the site renders (title, contest alias, canonical URL, TBA flags) and the Hudl linkage block. Videos and the gofan/NFHS stream URLs are media/commerce fields and 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_next_contest"
  }
}

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.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does useful work by disclosing what is deliberately excluded (videos, gofan/NFHS stream URLs) and by describing the derived-field block, but it says nothing about the empty case (no upcoming contest), auth requirements, or caching/freshness, which are the remaining risks for a read tool like this.

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?

Front-loaded with the one-line purpose, then a single dense sentence covering payload composition and exclusions. Every clause is informational rather than filler, though the field enumeration is long enough to be slightly heavy for a two-parameter read tool.

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?

There is no output schema, so the description must describe the return value, and it does so with reasonable specificity (contest fields, derived fields, Hudl block, excluded media fields). The main omission is the no-upcoming-contest behavior, which matters for a 'next' query but is a narrow gap given how much of the payload shape is spelled out.

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 descriptions plus concrete example ids, so the schema already does the parameter work. The description adds no meaning about teamId or sportSeasonId (e.g. that the season id must belong to that exact team and level) beyond what is already written in the schema.

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?

States a specific verb and resource: returns a single team season's next-contest box, and enumerates what that box contains (contest fields, derived site fields, Hudl linkage). It implicitly separates itself from maxpreps_team_schedule by naming the 'next contest' scope and by referencing the schedule tool's contest shape, though it never explicitly contrasts the two.

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 'next contest' framing rather than stated: there is no explicit 'use this when you need only the upcoming game, use maxpreps_team_schedule for the full season' routing, and no guidance on prerequisites beyond the schema's id sourcing. The agent can infer intent, but must do so itself.

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