Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_states

Read-only

Get MaxPreps states and areas taxonomy. Returns the complete MaxPreps state/area taxonomy: 54 records covering the 50 US states, the District of Columbia, National (NN), Prep Schools (PS) and Mexico. Each record carries the state GUID, code, long name, section/division naming aliases, governing-body identity and time zone. This is the discovery surface for the stateCode enum every other MaxPreps route accepts.

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": "maxpreps_states"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context beyond them: the exact record count (54), the enumeration contents, and the field composition of each record (GUID, code, long name, aliases, governing body, time zone). It does not discuss caching or stability of the taxonomy, which would be the next useful detail.

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 sentences, front-loaded with the verb and resource, then scope, then role. There is minor redundancy between 'states and areas taxonomy' and 'the complete MaxPreps state/area taxonomy' in the second sentence, but no filler beyond that.

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?

With no parameters, an output schema present, and annotations covering safety, the remaining burden is scope and role — both stated precisely, including the exact enumeration membership that an agent might otherwise have to discover by calling the tool.

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?

The tool takes zero parameters, so the baseline is 4 and nothing about parameter meaning needs compensating for. The description correctly spends its words on output shape instead of inventing input guidance.

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 plus resource ('Get MaxPreps states and areas taxonomy') and an explicit enumeration of scope: 54 records covering 50 states, DC, National (NN), Prep Schools (PS), and Mexico. The final sentence distinguishes its role from every other MaxPreps route as the source of the stateCode enum.

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?

'This is the discovery surface for the stateCode enum every other MaxPreps route accepts' tells the agent exactly when to call it: before any other MaxPreps route that takes a state code. It stops short of naming or excluding the adjacent sibling state tools (nfhs_states, wta_match_states), leaving that routing 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