Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_team_next_contest

Read-only

Get 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
teamIdYesRequired team id from maxpreps-school-search or maxpreps-team.
sportSeasonIdYesRequired sport-season id for that exact team and level.

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

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

Annotations already cover read-only and open-world behavior, so the description's real value is the disclosure of what the payload contains (contest core, derived site fields, Hudl linkage) and what is deliberately excluded (videos, gofan/NFHS stream URLs). That exclusion note is a useful boundary condition for callers. It does not add auth, rate-limit, or pagination context, which keeps it short of a 5.

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 a one-line purpose statement, then a structured explanation of contents and exclusions. It is dense but not padded; the list of returned fields is arguably longer than necessary since the output schema covers them, which keeps it from a 5.

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 and 100% parameter coverage, the description only needs to frame scope and boundaries, which it does. It covers what is returned, what is omitted, and the relationship to the schedule shape. Missing only explicit usage routing against sibling tools.

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 in the schema, so the baseline is 3. The description's phrase 'one team season's' and 'for that exact team and level' reinforces the pairing but adds no new syntax, format, or constraint detail.

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?

States a specific verb and resource ('Get MaxPreps team next contest') and scopes it to 'one team season's next-contest box', which separates it from the full-schedule sibling maxpreps_team_schedule. It also names the sibling whose contest shape is reused, making the scope boundary explicit.

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 name and the 'next-contest' framing, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of when to prefer maxpreps_team_schedule or maxpreps_team_context instead. An agent can infer the case but gets no routing rules.

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