Crawlora MCP

nfhs_highlights

Read-only

Search NFHS Network published highlight clips and return title, headline, subtitle, date, duration, publisher identity and logo, sport, game type, gender, level, categories and thumbnail. Filter by activity display name from nfhs_activities, state, gender and level from nfhs_filters, school_key, a free-text search_term (at least 3 characters) or a YYYY-MM-DD from/to date range; sort by date or created_at. start/size page and next_cursor is the reliable deep-page cursor; 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_highlights"
  }
}

Input Schema

Name	Required	Description
`to`	No	Optional inclusive date upper bound as YYYY-MM-DD.
`from`	No	Optional inclusive date lower bound as YYYY-MM-DD.
`size`	No	Optional page size, 1 to 500; defaults to 20.
`sort`	No	Optional sort order: date+asc, date+desc or created_at+desc.
`level`	No	Optional level filter.
`start`	No	Optional zero-based result offset; use next_cursor for deep pages.
`state`	No	Optional two-letter state code.
`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.
`school_key`	No	Optional school key from nfhs-schools.
`search_term`	No	Optional free-text term matched against highlight titles; 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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral detail beyond that: default paging via start/size, next_cursor as the reliable deep-page mechanism, and the empty-match contract ('count 0 with an empty list'). It doesn't mention auth requirements, rate limits, or whether filters combine as AND, which keeps it below a 5.

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?

Purpose and return fields are front-loaded, then filters, sorting, paging, and the empty-result contract follow in a logical order. It is one dense semicolon-chained sentence rather than structured bullets, which hurts scannability slightly but wastes almost no words.

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?

An output schema exists, so listing every returned field is mild redundancy, but the description covers the parts an agent genuinely needs: valid filter sources, the sort whitelist, page-size semantics, and cursor-based deep paging. The main remaining gap is that filter combination semantics (AND vs. OR) and behavior when conflicting filters are supplied are not stated.

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 is already documented with format, defaults, and constraints (e.g. search_term minimum 3 characters, YYYY-MM-DD dates, size 1-500). The description largely restates those same facts; its only marginal addition is tying activity/gender/level/school_key to the discovery endpoints that supply valid values. Baseline 3 is appropriate.

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 published highlight clips') and immediately enumerates what comes back (title, headline, subtitle, date, duration, publisher, sport, game type, gender, level, categories, thumbnail). The NFHS Network scoping plus references to nfhs_activities/nfhs_filters/nfhs_schools makes it distinguishable from the other provider highlight tools in the sibling list.

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?

It tells the agent where filter values come from (activity display name from nfhs_activities, gender/level from nfhs_filters, school_key from nfhs_schools) and when to use next_cursor instead of start. It doesn't say when NOT to use this tool or name a sibling like nfhs_search as the alternative for non-highlight content, so it stops short of explicit routing.

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.