Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nfhs_associations

Read-only

Search NFHS Network state high-school associations and sections and return each record's key, slug, name, acronym, timezone, colours, social links, state coverage and publisher/producer identities. Use search_term (at least 3 characters) to match names or acronyms, state to narrow by state, and start/size to page; next_cursor is the reliable deep-page cursor. Then call nfhs_association with the key or slug 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_associations"
  }
}

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 associations that are part of the NFHS Network.
search_termNoOptional free-text term matched against association names and acronyms; 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 already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the exact field set returned per record, the reliable-cursor vs. offset distinction, and the semantics of a valid empty match. It stops short of noting rate limits or result-shape caveats, but the gap is small.

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 compact sentences, front-loaded with the purpose and return fields before moving to parameters and the follow-up call. Information density is high and little is wasted, though the field enumeration is somewhat long relative to its value given an output schema exists.

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 return values need not be spelled out, yet the description covers usage, paging strategy, follow-up routing, and empty-result behavior — everything needed to invoke it correctly. The only omission is any mention of the is_network filter, which is a minor incompleteness for a tool of this complexity.

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 baseline is 3. The description largely restates what the schema already says (search_term minimum length, state narrowing, start/size paging) and adds only the next_cursor paging advice, which is not an input property at all. Notably it never mentions the is_network flag, so one documented filter gets no descriptive reinforcement.

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 state high-school associations and sections") and enumerates the record fields returned. The trailing instruction to call nfhs_association for a single record makes the distinction from the singular sibling unmistakable.

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 states exactly how to use each filter (search_term for names/acronyms, state to narrow, start/size to page), names next_cursor as the preferred deep-paging mechanism, and routes the agent to nfhs_association with a key or slug for detail. It also defines the empty-result case (count 0 with an empty list), leaving nothing to inference.

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