Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nfhs_schools

Search NFHS Network schools by state and optional name, returning paginated identity, location, colors, logo, and network flags for school lookup and directory research.

Instructions

Search NFHS Network schools. Returns one page of schools with identity, mascot, acronym, address, city, state, coordinates, colours, logo, network/subscription flags, publisher and producer keys and share image. Search within a state (recommended) and optionally by school name with search_term (at least 3 characters), sorted by school_name+asc or school_name+desc; page with start/size and use next_cursor for deep pages. Use nfhs-suggest for typeahead and nfhs-school for one record by key or slug.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nfhs_schools"
  }
}

Input Schema

Name	Required	Description
`size`	No	Page size, 1 to 500; defaults to 20
`sort`	No	Sort order: school_name+asc or school_name+desc
`start`	No	Zero-based result offset
`state`	No	Two-letter state code from nfhs-states; without it the national school index is searched
`is_network`	No	Optional network flag filter; true returns schools that are part of the NFHS Network
`search_term`	No	Free-text term matched against school names; at least 3 characters

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it lists the returned fields, states that results are one page, documents pagination via start/size and next_cursor, and notes that omitting state searches the national index. It stops short of stating cost/latency or page-size ceilings, but the behavioral profile is largely clear.

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?

Front-loaded with purpose, then scope, then alternatives, in a single dense paragraph with no filler sentences. The long enumeration of return fields is somewhat list-like but each item earns its place by substituting for an absent output schema.

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?

Six optional parameters, no required ones, and no output schema, so the description appropriately spends effort describing the return fields and pagination. The only real gap is the undocumented is_network filter and the phantom next_cursor reference, both of which could confuse an agent assembling a call.

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 most parameter meaning is already structured. The description adds real guidance (state first, then optional name filter, paging strategy), but it omits is_network entirely and references a next_cursor parameter that does not appear in the input schema, which can mislead about how deep paging is actually requested.

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?

States a specific verb and resource ("Search NFHS Network schools") plus the return shape, and explicitly distinguishes itself from nfhs-suggest (typeahead) and nfhs-school (single record by key or slug). An agent can pick this tool over its siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit recommended usage pattern ("Search within a state (recommended)"), the optional narrowing condition (search_term of at least 3 characters), sort options, and named alternatives with the conditions that select them. Nothing about when-to-use is left to inference.

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

Deploy Server