Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nfhs_affiliates

Search NFHS Network broadcast affiliates by name or state, filter by network status, and page through results to retrieve identity, coverage, social, and subscription details.

Instructions

Search NFHS Network broadcast affiliates. Returns one page of broadcast affiliates with identity, type, network and subscription flags, attribution group, colours, social links and state coverage. Search by name with search_term (at least 3 characters) or filter by state; page with start/size and use next_cursor for deep pages. Use nfhs-affiliate 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_affiliates"
  }
}

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 affiliates that are part of the NFHS Network
`search_term`	No	Free-text term matched against affiliate names; 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 disclosure burden, and it does well: it enumerates the returned fields (identity, type, network and subscription flags, attribution group, colours, social links, state coverage) and explains pagination depth behavior. It stops short of stating read-only semantics explicitly or any rate limits/authorization requirements, which leaves a modest gap for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with purpose and return shape, followed by usage and the sibling alternative; there is no filler. Density is high but each clause carries information the agent needs.

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 compensates by listing the fields returned and describing pagination, so the agent can call it confidently. The only substantive hole is the dangling next_cursor reference, which is not backed by any schema parameter.

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 the schema already documents all five parameters, and the description largely restates them (search_term minimum length, state filtering, start/size). Notably it instructs the agent to 'use next_cursor for deep pages' even though no next_cursor property exists in the input schema, which muddies rather than clarifies parameter usage.

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 broadcast affiliates') and immediately follows with the return shape, so an agent knows this is a paginated list/search endpoint rather than a single-record fetch. It explicitly separates itself from the singular sibling by naming nfhs-affiliate for single-record retrieval.

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 gives concrete selection rules: use search_term (with a minimum of 3 characters) to search by name, or filter by state, and use nfhs-affiliate when a single record by key or slug is wanted. Paging guidance (start/size, next_cursor for deep pages) is stated rather than inferred.

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

Deploy Server