Crawlora MCP

nfhs_events

Read-only

Search NFHS Network games and events in the live, upcoming or on-demand drill-down and return schedule, sport, game type, gender, level, scores, status, postseason flag, participant teams and publisher identities. Filter by activity display name from nfhs_activities, state from nfhs_states, gender and level from nfhs_filters, school_key, publisher_key, a free-text search_term (at least 3 characters) or a YYYY-MM-DD from/to start-date range; sort by start_time or date. start/size page and next_cursor is the reliable way past 10000 results. Use nfhs_event for the full detail of one key; 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_events"
  }
}

Input Schema

Name	Required	Description
`to`	No	Optional inclusive start-date upper bound as YYYY-MM-DD.
`from`	No	Optional inclusive start-date lower bound as YYYY-MM-DD.
`size`	No	Optional page size, 1 to 500; defaults to 20.
`sort`	No	Optional sort order: start_time+asc, start_time+desc, date+asc, date+desc or updated_at+desc.
`type`	No	Event drill-down: live, upcoming or ondemand. Defaults to upcoming.
`level`	No	Optional level filter: varsity, junior varsity, freshman, sophomore or middle school.
`start`	No	Optional zero-based result offset; use next_cursor for deep pages.
`state`	No	Optional two-letter state code; use the nfhs-states discovery endpoint for the complete list.
`cursor`	No	Optional next_cursor from a previous page; the reliable way to page beyond the first 10000 results.
`gender`	No	Optional gender filter: boys, girls or coed.
`activity`	No	Optional activity name exactly as the nfhs-activities discovery endpoint reports it, matched case-insensitively, for example Football or Ice Hockey.
`school_key`	No	Optional school key from nfhs-schools; returns that school's games.
`search_term`	No	Optional free-text term matched against event titles and team names; at least 3 characters.
`is_postseason`	No	Optional postseason flag filter; true returns playoff and championship events only.
`publisher_key`	No	Optional publisher key from an event's publishers list.
`download_to_own`	No	Optional download-to-own filter; true returns events whose broadcast can be downloaded for ownership.

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, yet the description still adds real behavioral context: a 10000-result pagination ceiling with cursor as the reliable escape hatch, and the semantics of a valid empty match ('count 0 with an empty list'). It does not discuss rate limits, required auth, or ordering of the returned list, so it adds meaningful but not exhaustive context on top of the annotations.

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 the capability and return surface, then filters, then paging, then the sibling hand-off — a logical progression. It is, however, one very long run-on sentence with heavy semicolon chaining, and some clauses duplicate the schema rather than earning their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter, zero-required search tool with full schema coverage, an output schema, and read-only annotations, the description covers the remaining gaps an agent needs: paging limits, empty-result semantics, filter provenance, and the list-vs-detail routing. Nothing material is missing for correct invocation.

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 every parameter's meaning is already documented, and the description largely restates it (filters, search_term minimum length of 3 characters, YYYY-MM-DD range, sort options). The one value-add is naming which discovery endpoint feeds each filter, which the schema also does, so baseline 3 applies.

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?

Opens with a specific verb and resource ('Search NFHS Network games and events') and enumerates the returnable fields (schedule, sport, game type, gender, level, scores, status, postseason flag, teams, publishers). It explicitly distinguishes itself from the sibling nfhs_event ('Use nfhs_event for the full detail of one key'), so an agent can pick the list-vs-detail 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 Guidelines4/5

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

Gives concrete routing guidance to the detail sibling and names the discovery siblings (nfhs_activities, nfhs_states, nfhs_filters) that supply valid filter values, plus pagination advice ('next_cursor is the reliable way past 10000 results'). It stops short of stating exclusions such as when not to filter by free text or what to do when a filter combination is unsupported, so it is clear but not fully explicit about when-not.

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.