Crawlora MCP

Official

by Crawlora-org

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

nfhs_search

Search NFHS Network schools, associations, and games by term, then filter results by state or activity.

Instructions

Free-text search across NFHS Network entities. Returns one page of mixed-entity search results for a term of at least 3 characters. Each item's content_type identifies its shape: school items carry school identity and location fields, state_association items carry association identity, and game items carry game scheduling fields. Optionally filter by state from nfhs-states or activity from nfhs-activities; page with start/size and use next_cursor for deep pages. Use the entity-specific routes when the type is known.

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": {
      "search_term": "<search_term>"
    },
    "name": "nfhs_search"
  }
}

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
`cursor`	No	next_cursor from a previous page; the reliable way to page beyond 10000 results
`activity`	No	Activity name from nfhs-activities, matched case-insensitively
`search_term`	Yes	Free-text term matched across school, association and game names; at least 3 characters

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.4/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 disclose meaningful behavior: results are paginated to one page, item shape varies by content_type, and deep paging should use next_cursor. It does not cover authentication or the server-side detail that start beyond 10000 results is unreliable (that detail lives only in the schema), so a small behavioral gap remains.

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?

Roughly four sentences, front-loaded with purpose and result shape, then filtering, then the alternative-route rule. The content_type enumeration is dense but earns its place because it defines the polymorphic response.

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 six-parameter search with no output schema, the description gives enough to call it correctly and to interpret the polymorphic result items. It stops short of describing ordering, total-result counts, or empty-result behavior, which would matter for a mixed-entity search.

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 all six parameters are already documented, and the description largely restates them (state from nfhs-states, activity from nfhs-activities, start/size paging, cursor for deep pages). It adds only light cross-referencing value, which is the baseline for a fully documented schema.

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 (free-text search across NFHS Network entities) and immediately describes the shape of the response as one page of mixed-entity results. It goes further by explaining what each content_type means (school, state_association, game), so an agent knows what it will get back without opening a 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?

The final sentence explicitly routes the agent away from this tool when the entity type is already known ('Use the entity-specific routes when the type is known'), which is the key selection decision against siblings like nfhs_schools or nfhs_events. It also states prerequisites: term of at least 3 characters, and state/activity values must come from nfhs-states/nfhs-activities.

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

Deploy Server