Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

maxpreps_tournament_sports

List sports with published tournament brackets, returning each sport's display name and playoffs URL, with optional state code filtering.

Instructions

MaxPreps tournament sports. Returns the sports the upstream publishes tournament (playoff) brackets for, with each sport's display name and canonical playoffs URL. Optionally scope the list to one state with stateCode.

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

Input Schema

NameRequiredDescriptionDefault
stateCodeNoOptional state code from maxpreps-states to scope the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description still discloses that this is a list retrieval, what each item contains, and how stateCode scopes results. It does not cover permissions, pagination/rate limits, error behavior, or what happens when stateCode is omitted.

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 three tight sentences, front-loads the purpose and output details, and contains no obvious filler. The initial fragment is acceptable given the surrounding specificity.

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?

For a one-parameter read-only retrieval tool with no output schema, the description sufficiently covers purpose, returned fields, and optional scoping. Minor gaps like pagination/error behavior and explicit sibling routing keep it from being fully complete.

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%, and the stateCode enum already defines allowed values. The description repeats the optional state scoping but adds little beyond the schema's own explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource, sports with tournament/playoff brackets, and states the returned fields: display name and canonical playoffs URL. It is distinguishable from a generic sports list, though it does not explicitly contrast with sibling maxpreps_sports.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the optional stateCode scoping but does not say when to choose this tool over maxpreps_sports or other tournament-related siblings. Usage is implied rather than explicitly guided.

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