Crawlora MCP

maxpreps_school_proximal

Read-only

Get MaxPreps schools near a school. Returns the MaxPreps schools near one school, using that school as the proximity origin, with the same school record shape as maxpreps-school-search: identity, location, colours, mascot, enrollment and each school's sport-season ids. Offset pagination with maxResults and startFrom; optional name, distance, ZIP, season and state-scope filters.

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_proximal"
  }
}

Input Schema

Name	Required	Description
`byState`	No	Optional search-by-state flag.
`zipCode`	No	Optional five-digit US ZIP code to narrow the radius.
`schoolId`	Yes	Required school id used as the proximity origin.
`sortOrder`	No	Optional sort order. Values: Distance, Name. Defaults to the upstream's distance ordering.
`startFrom`	No	Optional zero-based offset for offset pagination. Defaults to 0.
`maxResults`	No	Optional page size from 1 to 200. Defaults to 50.
`searchText`	No	Optional school-name filter inside the radius.
`allSeasonId`	No	Optional all-season id from maxpreps-sports to scope the returned teams.
`maxDistance`	No	Optional maximum distance in metres from the origin school.
`publishedOnly`	No	Optional published-only flag.
`sportSeasonId`	No	Optional sport-season id to scope the returned teams.
`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 and the bar is lower. The description adds real behavioral context beyond that: the exact record shape returned (identity, location, colours, mascot, enrollment, sport-season ids) and the offset-pagination model with maxResults/startFrom and their defaults. It does not mention rate limits or failure behavior for an invalid schoolId, which keeps it below 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?

Three sentences, front-loaded with the core action and the origin semantics before the pagination and filter details. There is mild redundancy between 'near a school' and 'near one school, using that school as the proximity origin', but the density of useful facts per sentence is high.

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 13-parameter proximity search with a required origin, the description states the origin semantics, return shape, and pagination model, and an output schema exists so return values need no further explanation. The remaining gaps (behavior with an unknown schoolId, whether a default radius applies) are minor for this tool class.

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 every parameter is already documented in the schema and the baseline is 3. The description groups the filters ('name, distance, ZIP, season and state-scope filters') and adds slight meaning by framing name as filtering 'inside the radius' and ZIP as narrowing it, but this is largely a restatement of schema text rather than new semantics.

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 and resource ('Get MaxPreps schools near a school') and immediately clarifies that the given school is the proximity origin, so the agent knows exactly what this returns. It also anchors the output shape to the sibling maxpreps_school_search record format. It stops short of naming when to prefer this over maxpreps_school_zip_search or maxpreps_school_search, so it is clear but not fully sibling-differentiated.

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: an agent can infer this is for proximity lookups from a known schoolId, and it lists available narrowing filters. However there is no explicit 'use this instead of X when Y', and no guidance on prerequisites such as needing a valid school id from maxpreps_school_search first.

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.