Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_school_contests

Retrieve a school's recent and upcoming contests across sports, including teams, scores, results, records, dates, level, and state, by school ID to review schedules and outcomes.

Instructions

MaxPreps school recent and upcoming contests. Returns a school's recent and upcoming contests across sports: contest id, canonical URL, timestamp, sport/gender/season/year, team level, contest state, TBA flags, home/away type and both teams with score, result and record. The source caps the list with maxLimit and returns the most relevant contests first.

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": {
      "schoolId": "<schoolId>"
    },
    "name": "maxpreps_school_contests"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxLimitNoMaximum number of contests from 1 to 100; defaults to 25 example(5)
schoolIdYesSchool id from maxpreps-school-search or maxpreps-school-zip-search example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)

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 burden. It does useful work by disclosing the returned field set, that the source enforces a cap, and the ordering ("most relevant contests first"), but it says nothing about permissions, pagination, truncation signaling, or how to tell whether results were cut off by maxLimit.

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 purpose followed by the return contract, with no filler. The long field enumeration is dense but each item earns its place for an output-schema-less 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?

No output schema exists, so the description must describe return values, and it does so thoroughly (contest id, URL, timestamp, sport/gender/season, level, state, TBA, home/away, both teams with score/result/record). The remaining gap is behavioral: no note on what happens when maxLimit truncates the set or how ordering interacts with it.

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 coverage is 100%, so both parameters are already documented with ranges and examples, making 3 the baseline. The description adds only marginal meaning — that maxLimit is enforced by the source rather than applied client-side — but offers nothing new about schoolId beyond what the schema states.

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-plus-resource framing ("Returns a school's recent and upcoming contests across sports") and enumerates the returned fields, so the agent knows exactly what it gets. It does not name a sibling such as maxpreps_team_schedule or maxpreps_team_next_contest to disambiguate the overlapping scope, which keeps it below a 5.

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 "school recent and upcoming contests" and by the mention of maxLimit capping the list, but there is no explicit when-to-use or when-not-to-use statement, no mention of prerequisites (schoolId must come from a search tool), and no routing to a sibling for a narrower team-level schedule.

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