Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_school_zip_search

Find MaxPreps schools near a five-digit US ZIP code with school details, sports team IDs, and filters for name, city, or distance.

Instructions

List MaxPreps schools near a ZIP code. Returns the MaxPreps schools around one five-digit US ZIP code 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 startFrom; optional name, city and distance filters. Use it when a caller starts from a location rather than a school name.

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": {
      "zipCode": "<zipCode>"
    },
    "name": "maxpreps_school_zip_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipCodeYesFive-digit US ZIP code example(90210)
startFromNoZero-based offset; defaults to 0 example(0)
searchCityNoOptional city filter example(Beverly Hills)
searchTextNoOptional school-name filter 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
searchByStateNoSearch by state instead of radius
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

A4.2/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 burden and does reasonably well: it discloses the return shape (identity, location, colours, mascot, enrollment, sport-season ids), that results are offset-paginated via startFrom, and that filters are optional. It omits operational traits such as whether includeDeleted/historicalOnly change record shape, error behavior on invalid or non-US ZIPs, and any permission or rate considerations.

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, all front-loaded: purpose, return shape and pagination, then the routing rule. Nothing redundant and no filler.

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 an eleven-parameter tool with no annotations and no output schema, the description supplies the essentials an agent needs — return shape, pagination mechanism, and selection guidance. The gap is the boolean flags (publishedOnly, searchByState, historicalOnly, includeDeleted), whose interactions and behavioral consequences are left entirely to one-line schema hints.

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 baseline is 3 and the schema already documents all eleven parameters including examples. The description adds only light framing — startFrom as offset pagination and the existence of name, city, and distance filters — without explaining interactions such as searchByState overriding maxDistance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource ('List MaxPreps schools near a ZIP code'), and the final sentence distinguishes it from the name-based sibling: 'Use it when a caller starts from a location rather than a school name.' An agent can separate this from maxpreps_school_search without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear selection condition tied to the caller's starting point (location vs. school name), which is exactly the ambiguity between this tool and maxpreps_school_search. It stops short of naming any other alternative (e.g. proximal or state-based lookups) or stating when not to use it, so it is clear context rather than exhaustive routing.

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