Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_tournament_sports

Read-only

Get 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 tournament sports list.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real context beyond them: the list is a filtered upstream view limited to sports with published playoff brackets, and each entry carries a display name plus canonical playoffs URL, telling the agent what to expect in the payload.

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 short sentences, front-loaded with what the tool returns, then the scope qualifier, then the optional parameter. No redundant restatement of the name and no filler.

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?

With an output schema present, the description need not enumerate return fields, and it covers purpose, scope, and the lone parameter. Only the missing comparison to the sibling sports tool keeps it from being fully complete for an agent choosing between them.

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% for the single stateCode parameter, so the baseline is 3. The description reinforces that it is an optional scoping filter, but the meaningful extra detail (state codes originate from maxpreps-states) lives in the schema, not the description.

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?

Specific verb plus resource ('Get MaxPreps tournament sports') followed by a precise scope statement: the subset of sports for which the upstream publishes playoff brackets, returned with display name and canonical playoffs URL. The narrower scope implicitly separates it from maxpreps_sports, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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 says the state scope is optional and how to use stateCode, which implies the use case (listing tournament-eligible sports, optionally for one state). It never states when to prefer this over maxpreps_sports or what happens if a state has no tournament sports, so the guidance is implied rather than explicit.

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