Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

nfhs_affiliate

Retrieve a single NFHS Network broadcast affiliate by key or slug to view its type, network and subscription flags, attribution group, colors, social links, and state coverage.

Instructions

Get one NFHS Network broadcast affiliate. Returns one broadcast affiliate by its key or slug, including its type, network and subscription flags, attribution group, colours, social links and state coverage. Use nfhs-affiliates to discover the key or slug first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "nfhs_affiliate"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes	Affiliate key or slug, for example prepspin or 00bf21ab8d

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose what comes back (type, network and subscription flags, attribution group, colours, social links, state coverage), which compensates for the missing output schema, but says nothing about error behavior for an invalid key, auth needs, or rate limits.

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 short sentences, front-loaded with the purpose and followed by the return contents and the discovery hint. There is mild redundancy between 'Get one broadcast affiliate' and 'Returns one broadcast affiliate by its key or slug', but nothing extraneous.

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 single-parameter lookup with no output schema, the description is nearly self-sufficient: it names the identifier, the fields returned, and how to obtain the identifier. Only error/empty-result behavior and auth expectations are unaddressed.

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% and the single 'key' parameter is already documented with examples (prepspin, 00bf21ab8d). The description only restates that key or slug is accepted, adding no format or fallback detail beyond the schema, 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?

Specific verb and resource: 'Get one NFHS Network broadcast affiliate', with the lookup key stated. It is clearly the singular counterpart to the sibling 'nfhs_affiliates' list tool, so an agent can distinguish them without opening a 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 an explicit prerequisite: 'Use nfhs-affiliates to discover the key or slug first', which routes the agent to the right sibling when the identifier is unknown. It does not state when-not to use it (e.g. bulk retrieval of many affiliates), so it stops short of full when/when-not guidance.

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

Deploy Server