Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_affiliate

Read-only

Get one NFHS Network broadcast affiliate by key or slug and return its type, network and subscription flags, attribution group, colours, social links and state coverage. Use nfhs_affiliates to discover the key or slug first; an unknown key is a 404.

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

NameRequiredDescriptionDefault
keyYesAffiliate key or slug from nfhs-affiliates, for example prepspin or 00bf21ab8d.

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.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: it names the return categories and discloses that an unknown key produces a 404, though it does not describe auth requirements, rate limits, or response shape in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states the lookup first, then the returned fields, then the discovery prerequisite and error behavior. Every sentence contributes to correct invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this is a simple one-parameter lookup with annotations and an output schema, the description supplies what an agent needs: the resource being fetched, the identifier source, the returned field categories, and the failure behavior. No critical context is missing.

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 single key parameter is already fully documented in the schema, including the slug example. The description reinforces that key is a lookup identifier from nfhs_affiliates and adds the 404 behavior, but it does not add syntax or format meaning beyond the schema.

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 states a specific verb and resource: get one NFHS Network broadcast affiliate by key or slug. It also makes the scope clear by identifying the returned fields and by distinguishing the lookup from the sibling discovery tool nfhs_affiliates.

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 explicitly says to use nfhs_affiliates to discover the key or slug first, and it states the failure mode: an unknown key is a 404. That gives an agent both the prerequisite and the error condition for selecting this tool correctly.

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