Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_affiliates

Read-only

Search NFHS Network broadcast affiliates and return each record's key, slug, name, affiliate type, network and subscription flags, attribution group, colours, social links and state coverage. Use search_term (at least 3 characters) or state to narrow and start/size to page; next_cursor is the reliable deep-page cursor. Then call nfhs_affiliate for one record. 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_affiliates"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoOptional page size, 1 to 500; defaults to 20.
startNoOptional zero-based result offset; use next_cursor for deep pages.
stateNoOptional two-letter state code; use the nfhs-states discovery endpoint for the complete list.
is_networkNoOptional network flag filter; true returns affiliates that are part of the NFHS Network.
search_termNoOptional free-text term matched against affiliate names; at least 3 characters.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description's added notes on pagination reliability, the enumerated return fields, and the count-0/empty-list semantics are genuinely useful behavior beyond structured fields. It stops short of stating rate limits, ordering, or whether subscription flags can be null, so it is strong but not exhaustive.

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?

Three front-loaded sentences with no filler: purpose and return shape first, then query mechanics, then the sibling routing and empty-result edge case. The long field enumeration in sentence one is partly redundant with the output schema, which is the main wasted space.

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 five-optional-parameter list tool with a full schema and an output schema, the description covers narrowing, paging, empty results and the follow-up tool, which is nearly everything an agent needs. The gap is that it references "next_cursor" as a deep-page cursor even though no such input property exists in the schema, and it omits the is_network filter.

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 coverage is 100%, so the schema already explains size, start, state, is_network and search_term; the description largely restates the search_term length rule and the start/size paging. It never mentions the is_network filter, which is only documented in the schema, so it adds little meaning beyond structured data.

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 broadcast affiliates") and enumerates the record shape returned, then explicitly separates this list operation from the single-record sibling nfhs_affiliate. An agent can distinguish it from nfhs_affiliate or nfhs_states without opening any 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?

Gives concrete narrowing options (search_term with a minimum length, or state), paging mechanics (start/size, next_cursor for deep pages), and an explicit hand-off rule ("Then call nfhs_affiliate for one record"). It also defines the empty-result condition so the agent does not retry a legitimately empty match.

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

All Crawlora MCP toolsInspect
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.

Resources