Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_school_search

Search MaxPreps schools by name to retrieve school records, locations, colors, mascots, enrollment, and team sportSeasonIds, enabling school and team discovery.

Instructions

Search MaxPreps schools by name. Searches MaxPreps schools by name and returns school records with identity, location, colours, mascot, enrollment and the sport-season ids of the school's teams. Offset pagination with maxResults and startFrom; sortOrder Name sorts alphabetically, Distance requires schoolId and returns rows nearest to that school. This is the primary discovery surface for schoolId and team sportSeasonId values.

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": {
      "query": "<query>"
    },
    "name": "maxpreps_school_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSchool-name search text; * browses the whole directory example(lincoln)
zipCodeNoOptional five-digit US ZIP code example(90210)
schoolIdNoSchool id used as the distance origin; required when sortOrder is Distance example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)
sortOrderNoSort order: Distance or Name; Distance requires schoolId
startFromNoZero-based offset; defaults to 0 example(0)
maxResultsNoPage size from 1 to 200; defaults to 50 example(25)
allSeasonIdNoOptional all-season id from maxpreps-sports to scope returned teams example(22e2b335-334e-4d4d-9f67-a0f716bb1ccd)
publishedOnlyNoOnly published schools
historicalOnlyNoOnly historically published schools
includeDeletedNoInclude deleted schools

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does reasonably well: it discloses the returned field set, offset pagination via maxResults/startFrom, alphabetical vs. proximity sort semantics, and that Distance fails without a schoolId origin. It does not cover auth requirements, rate limits, or what includeDeleted/publishedOnly actually change about results.

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?

Four tight sentences, front-loaded with purpose then return shape then mechanics then strategic value. No filler, though the pagination/sort sentence duplicates what the schema already states and could be trimmed to just the behavioral nuance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, annotation-free, output-schema-free search tool, the description covers what an agent needs: what is searched, what fields return, how paging and sorting work, the Distance precondition, and why the caller should care (schoolId and sportSeasonId harvesting). Remaining gaps like rate limits are peripheral to correct invocation.

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%, so the schema already documents all ten parameters, including enum values and examples. The description largely restates structured data (maxResults/startFrom pagination, Distance requiring schoolId) rather than adding new meaning; only the framing of schoolId as a "distance origin" adds modest interpretive value. 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 opens with a specific verb+resource ("Search MaxPreps schools by name") and enumerates what comes back: identity, location, colours, mascot, enrollment, and team sportSeasonId values. It also positions itself as "the primary discovery surface for schoolId and team sportSeasonId values," which implicitly separates it from detail-oriented siblings like maxpreps_school. It stops short of naming an alternative tool outright, so it misses the top mark.

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 rather than stated: calling this first to obtain schoolId/team sportSeasonId is suggested by "primary discovery surface," and the Distance sort constraint ("requires schoolId and returns rows nearest to that school") is a concrete conditional. However, nothing tells the agent when to prefer maxpreps_school_zip_search or maxpreps_school_proximal over this tool, or when name search is inappropriate.

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