Crawlora MCP

nfhs_schools

Read-only

Search NFHS Network schools and return each school's key, slug, name, mascot, acronym, address, city, state, coordinates, colours, logo, network/subscription flags and publisher/producer identities. Use state from nfhs_states to search within a state (recommended), search_term (at least 3 characters) to match names, and school_name+asc or school_name+desc to sort; start/size page and next_cursor is the reliable deep-page cursor. Use nfhs_suggest for typeahead and nfhs_school for one record. A valid empty match is count 0 with an empty list.

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	Optional page size, 1 to 500; defaults to 20.
`sort`	No	Optional sort order: school_name+asc or school_name+desc.
`start`	No	Optional zero-based result offset; use next_cursor for deep pages.
`state`	No	Two-letter state code to search within; use the nfhs-states discovery endpoint for the complete list.
`is_network`	No	Optional network flag filter; true returns schools that are part of the NFHS Network.
`search_term`	No	Optional free-text term matched against school names; at least 3 characters.

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

A4.3/5.0

Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, but the description adds useful behavioral context: the full set of returned fields, the empty-result semantics as count 0 with an empty list, and pagination reliability. It does not discuss auth or rate limits, but the supplied annotations and output schema reduce the burden.

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 description is front-loaded with purpose and then moves efficiently into usage, alternatives, and edge-case behavior. The long return-field enumeration is somewhat redundant given the output schema, but overall it remains dense and purposeful.

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 search/list tool with annotations, full schema coverage, and an output schema, the description covers purpose, usage, alternatives, pagination, and empty-result behavior. The only notable gap is the mention of next_cursor without it appearing in the input schema.

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 documents all six parameters, including state, search_term, sort, start, and size. The description reinforces their intended use but also refers to next_cursor as a reliable deep-page cursor even though next_cursor is not a declared input parameter, creating a minor inconsistency.

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 description opens with a specific verb and resource: search NFHS Network schools. It enumerates the returned fields and explicitly contrasts list search with nfhs_suggest for typeahead and nfhs_school for a single record, so the tool is distinguishable from its siblings.

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?

It gives explicit guidance on using state from nfhs_states as recommended, search_term with at least three characters, sort syntax, page sizing, and the reliable deep-page cursor. It also names alternatives and their appropriate conditions, plus defines a valid empty match.

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.