Crawlora MCP

maxpreps_school_search

Read-only

Get 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

Name	Required	Description
`query`	Yes	Required school-name search text, for example lincoln. Use * to browse the whole directory.
`zipCode`	No	Optional five-digit US ZIP code to narrow the search.
`schoolId`	No	Optional school id used as the distance origin; required when sortOrder is Distance.
`sortOrder`	No	Optional sort order. Values: Distance, Name. Distance requires schoolId and returns rows nearest to that school; Name sorts alphabetically. Defaults to Name.
`startFrom`	No	Optional zero-based offset for offset pagination. Defaults to 0.
`maxResults`	No	Optional page size from 1 to 200. Defaults to 50.
`allSeasonId`	No	Optional all-season id from maxpreps-sports to scope the returned teams to one season.
`publishedOnly`	No	Optional published-only flag.
`historicalOnly`	No	Optional historical-only flag.
`includeDeleted`	No	Optional include-deleted flag.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, but the description goes further by listing the returned fields (identity, location, colours, mascot, enrollment, sport-season ids) and explaining pagination and sort semantics. It does not mention rate limits or result-size caveats, but the added behavioral context is substantial.

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?

The definition is dense but front-loaded: purpose first, then return contents, then pagination and sort rules, then the discovery-surface framing. The opening 'Get search MaxPreps schools by name' is slightly redundant phrasing, but no sentence is wasted.

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?

For a 10-parameter search tool with an output schema and read-only annotations, the description covers purpose, return shape, pagination, and sort behavior adequately. The three boolean flags (publishedOnly, historicalOnly, includeDeleted) are left to the schema, which is acceptable given full schema coverage.

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 every parameter including the sortOrder Distance/schoolId dependency is already documented in the schema, and the description largely restates those constraints rather than adding new meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ('Searches MaxPreps schools by name') and names what the tool returns, so an agent can distinguish it from a detail-fetch tool like maxpreps_school. It does not explicitly name the closely related siblings (maxpreps_school_zip_search, maxpreps_school_proximal) even though the distance-sort behavior overlaps with them, so differentiation is implied rather than stated.

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?

'This is the primary discovery surface for schoolId and team sportSeasonId values' gives a clear positive use case, and the note that Distance sorting requires schoolId states a prerequisite. There is no explicit when-not guidance or named alternative for the ZIP-code or proximity variants, leaving the agent to infer routing from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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.