Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_states

Returns MaxPreps state/area taxonomy records with GUIDs, codes, names, aliases, governing bodies, and time zones to identify valid stateCode values for other MaxPreps routes.

Instructions

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry behavior. It discloses a read-oriented taxonomy return with exact record count and field contents, making the operation and output scope transparent. It omits explicit side-effect/read-only language and any auth or rate-limit notes, but for a zero-parameter taxonomy getter the coverage is solid.

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 compact sentences front-load the taxonomy scope, then add record composition, field details, and consumer guidance. Every sentence earns its place and there is no filler.

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?

For a zero-parameter, no-output-schema taxonomy tool, the description gives record count, coverage, field contents, and the downstream enum use case. That is enough for an agent to call it correctly without an output schema.

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?

There are zero input parameters, so there is no parameter semantics to explain beyond the baseline. The description adds nothing misleading about parameters.

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 uses a specific verb ('Returns') and resource ('MaxPreps state/area taxonomy') and quantifies scope as 54 records covering 50 states plus DC, National, Prep Schools, and Mexico. This clearly distinguishes it as the MaxPreps stateCode discovery tool rather than a generic states endpoint.

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?

It explicitly identifies itself as the discovery surface for the stateCode enum accepted by every other MaxPreps route, giving a clear use case. However, it does not state when to choose a different states tool or any exclusion, so it is strong but not a full when/when-not/alternatives statement.

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