Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

nfhs_events

Search NFHS Network games and events by activity, state, gender, level, school, publisher, date range, or free text; filter live, upcoming, on-demand, postseason, and download-to-own broadcasts.

Instructions

Search NFHS Network games and events. Returns one page of games and events from the live, upcoming or on-demand drill-down with 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 or publisher_key, a free-text search_term (at least 3 characters) and a YYYY-MM-DD from/to start-date range; sort by start_time or date. Page with start/size and use next_cursor for deep pages. Use nfhs-event for the full detail of one event key.

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

NameRequiredDescriptionDefault
toNoInclusive start-date upper bound as YYYY-MM-DD
fromNoInclusive start-date lower bound as YYYY-MM-DD
sizeNoPage size, 1 to 500; defaults to 20
sortNoSort order: start_time+asc, start_time+desc, date+asc, date+desc or updated_at+desc
typeNoEvent drill-down: live, upcoming (default) or ondemand
levelNoLevel filter: varsity, junior varsity, freshman, sophomore or middle school
startNoZero-based result offset
stateNoTwo-letter state code from nfhs-states
cursorNonext_cursor from a previous page; the reliable way to page beyond 10000 results
genderNoGender filter: boys, girls or coed
activityNoActivity name from nfhs-activities, matched case-insensitively, for example Football
school_keyNoSchool key from nfhs-schools
search_termNoFree-text term matched against event titles and team names; at least 3 characters
is_postseasonNoOptional postseason flag filter; true returns playoff and championship events only
publisher_keyNoPublisher key from an event's publishers list
download_to_ownNoOptional download-to-own filter; true returns events whose broadcast can be downloaded for ownership

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

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 disclosure burden, and it does substantial work: it states results are a single page, names the default drill-down (upcoming), and explains that deep paging requires next_cursor rather than start offsets. It does not mention authentication, rate limits, or the result cap that sits in the schema, leaving some operational behavior undisclosed.

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?

A single dense paragraph that is front-loaded with purpose and result contents before moving to filters and paging, which is the right order for an agent. A few clauses duplicate the schema verbatim (the 3-character minimum, YYYY-MM-DD format), adding minor redundancy.

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 16-parameter tool with no output schema and no annotations, the description supplies the return-field inventory, the paging model, filter provenance and the detail-tool handoff. What remains thin is failure behavior and the deep-paging ceiling, which are only implied rather than stated here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by tying filters to their lookup tools ('state from nfhs-states', 'school_key or publisher_key') and by summarizing the sortable fields (start_time, date) and the 3-character search_term minimum. It largely restates the schema's enum-ish value lists, which keeps it from a 5.

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 immediately enumerates what a result carries (schedule, sport, scores, status, postseason flag, teams, publishers). It explicitly contrasts itself with the sibling 'nfhs-event', so an agent can distinguish the list tool from the single-event 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 clear routing: use nfhs-event for the full detail of one event key, and points to nfhs-activities, nfhs-states, nfhs-filters and nfhs-schools as the authoritative sources for filter values. It lacks an explicit exclusion against other search-like siblings such as nfhs_search or nfhs_highlights, so it stops short of the full when/when-not treatment.

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

Deploy Server

Other Tools