Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nfhs_associations

Search NFHS Network state high-school associations by name, acronym, or state and filter by network membership. Returns paginated records with acronym, timezone, coverage, social links, and championship URLs.

Instructions

Search NFHS Network state associations and sections. Returns one page of state high-school associations and their sections (for example GHSA or CIF - North Coast Section) with identity, acronym, timezone, colours, social links, state coverage, publisher and producer keys and championship page URL. Search by name or acronym with search_term (at least 3 characters) or filter by state; page with start/size and use next_cursor for deep pages. Use nfhs-association to fetch 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_associations"
  }
}

Input Schema

Name	Required	Description
`size`	No	Page size, 1 to 500; defaults to 20
`start`	No	Zero-based result offset
`state`	No	Two-letter state code from nfhs-states
`is_network`	No	Optional network flag filter; true returns associations that are part of the NFHS Network
`search_term`	No	Free-text term matched against association names and acronyms; 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?

No annotations are supplied, so the description carries the full disclosure burden; it does well by describing the result shape, the filter semantics, and the pagination model. It omits auth/permission requirements and rate limits, and it names a next_cursor pagination mechanism that does not appear in the input schema, which could mislead an agent attempting deep paging.

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 purpose followed by return contents and then usage routing, with no filler. The long enumeration of returned fields is dense but earns its place given there is no output schema; the next_cursor mention is the one piece of wasted, inaccurate wording.

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?

With no output schema and no annotations, the description does the necessary work by spelling out return fields and filter behavior. It falls short only on operational context (auth, rate limits) and on the phantom next_cursor pagination hint, which is the one thing an agent could act on incorrectly.

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 all five parameters already have descriptions and the baseline is 3. The description restates search_term's 3-character minimum, the state filter, and paging, but never mentions is_network, and it introduces next_cursor that the schema does not define, so it adds little meaning and a bit of confusion rather than clarification.

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 gives a specific verb and resource ("Search NFHS Network state associations and sections") and enumerates the returned fields (identity, acronym, timezone, colours, social links, state coverage, publisher/producer keys, championship URL). It explicitly names the sibling it is not, nfhs-association, so an agent can separate the list/search tool from the single-record tool 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 Guidelines5/5

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

It states the two selection paths (search_term with a 3-character minimum, or state filter), covers paging via start/size, and explicitly routes single-record lookups to nfhs-association by key or slug. The only rough edge is the reference to next_cursor for deep pages, which is not a documented parameter in the schema.

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

Deploy Server