Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nfhs_states

Retrieve all NFHS Network states and territories with their names, codes, and slugs to get the exact state code required by school, event, highlight, association, affiliate, and search filters.

Instructions

List NFHS Network states and territories. Returns the complete state list NFHS Network serves (52 values, including DC and the national "US" pseudo-state) with the name, code and slug used by state routes. Use it to obtain the exact state code the nfhs-schools, nfhs-events, nfhs-highlights, nfhs-associations, nfhs-affiliates and nfhs-search state filters accept. This endpoint takes no parameters.

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_states"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses result cardinality (52), the exact fields returned (name, code, slug), the inclusion of DC and a 'US' pseudo-state, and that the endpoint takes no parameters. It stops short of saying the list is static/unlikely to change, but for a zero-arg enumeration endpoint the behavioral picture is essentially complete.

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?

Three sentences, front-loaded with what it returns, then why to call it, then the no-parameter note. Nothing is redundant or padding.

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?

No output schema exists, but the description compensates by naming the returned fields and the value count, and it states the downstream consumer filters. An agent has everything needed to call it and use the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline applies; the description reinforces this with 'This endpoint takes no parameters,' which is accurate against the empty schema and prevents an agent from inventing a filter argument.

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?

States a specific verb and resource ('List NFHS Network states and territories') and pins down scope precisely: 52 values including DC and the 'US' pseudo-state. The NFHS naming separates it cleanly from sibling state lists like maxpreps_states and wta_match_states.

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 an explicit when-to-use: obtain the exact state code that the state filters of nfhs-schools, nfhs-events, nfhs-highlights, nfhs-associations, nfhs-affiliates and nfhs-search accept. That is a clear lookup-then-filter workflow with the consumers named.

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

Deploy Server

Other Tools