Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

maxpreps_school_proximal

Find MaxPreps schools near a specified school using it as the proximity origin, then filter by name, distance, ZIP, season, or state and paginate results.

Instructions

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

NameRequiredDescriptionDefault
byStateNoSearch by state instead of radius
zipCodeNoOptional five-digit US ZIP code example(90210)
schoolIdYesSchool id used as the proximity origin example(7bdc339f-7cbf-4728-b0c8-ed898929cf68)
sortOrderNoOptional sort order: Distance or Name
startFromNoZero-based offset; defaults to 0 example(0)
maxResultsNoPage size from 1 to 200; defaults to 50 example(25)
searchTextNoOptional school-name filter inside the radius example(lincoln)
allSeasonIdNoOptional all-season id from maxpreps-sports example(22e2b335-334e-4d4d-9f67-a0f716bb1ccd)
maxDistanceNoOptional maximum distance in metres example(40000)
publishedOnlyNoOnly published schools
sportSeasonIdNoOptional sport-season id to scope returned teams example(2286cd80-c46d-4739-8dd1-92a67ca8daa7)
historicalOnlyNoOnly historically published schools
includeDeletedNoInclude deleted schools

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, the description must carry the behavioral load; it does disclose read-only retrieval semantics by describing the returned record fields and pagination scheme (maxResults/startFrom). It does not address defaults for includeDeleted or publishedOnly, permission requirements, or result caps beyond the page size.

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 the core behavior, then the record shape and then pagination/filters. Minor redundancy in restating 'schools near a school' twice, but nothing that wastes meaningful space.

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 tool with no output schema, the description usefully enumerates the returned fields (identity, location, colours, mascot, enrollment, sport-season ids) and the pagination model, which is the main gap it needed to fill. Explicit default values for the boolean toggles are left to the schema, which is acceptable.

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 explains every one of the 13 parameters including examples and defaults. The description only groups them loosely ('name, distance, ZIP, season and state-scope filters') and adds no syntax or interaction detail beyond that baseline.

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 gives a specific verb and resource ('Returns the MaxPreps schools near one school') plus the key scoping concept: the supplied school acts as the proximity origin. It also ties the output shape to maxpreps_school_search, which helps distinguish the two, though it never states outright that plain lookups belong to the sibling tool.

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 'near a school' and the enumeration of optional filters, so an agent can infer this is the radius/state-proximity discovery tool. However, there is no explicit 'use X when' or 'do not use this for Y' routing against maxpreps_school_search or maxpreps_school_zip_search.

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