Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_school_contests

Read-only

Get 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
maxLimitNoOptional maximum number of contests from 1 to 100. Defaults to 25.
schoolIdYesRequired school id from maxpreps-school-search or maxpreps-school-zip-search.

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

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine behavioral context: results are capped by the source, most relevant contests come first, and TBA flags exist. It does not state pagination or whether results are truncated silently, but the ordering and cap disclosure is meaningful beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the verb and resource, then the payload fields, then the cap/ordering caveat. No filler; the field enumeration earns its place by telling the agent what to expect in the payload.

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?

Complete for a two-parameter read tool: purpose, cap behavior, ordering, and payload contents are all stated, and an output schema exists to define return shapes. The enumerated return fields are partly redundant with that output schema, which is the only real excess.

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%, including the maxLimit range and default of 25, so the schema does the heavy lifting. The description only echoes the cap behavior, adding no further syntax or format detail; baseline 3 is appropriate.

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 ('Get MaxPreps school recent and upcoming contests') and clarifies the scope is across sports for a single school. It does not explicitly name a sibling alternative (e.g. a team-level schedule tool), so an agent must infer the school-vs-team distinction from names alone.

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: an agent infers it should call this when it wants a school's recent and upcoming contests. There is no explicit when-to-use, when-not-to-use, or alternative routing guidance, and no precondition statement beyond the schema's note on schoolId provenance.

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