Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_scoreboard

Read-only

Get MaxPreps scoreboard contest ids by date. Returns the scoreboard for one context (National, State, Section, StateDivision, Association, League or DMA) and one genderSport and level: the yesterday/today/tomorrow scoreboard canonical URLs and the contest ids grouped by date. Use the ids to discover which games exist on a date; this route returns the id index, not the contest detail.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "genderSport": "<genderSport>",
      "level": "<level>"
    },
    "name": "maxpreps_scoreboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoContext identifier: a state code for National (use NN) and State, or a section/state-division/association/league/DMA id for the other contexts.
levelYesRequired team level. Values: Varsity, JV, Freshman.
contextYesRequired scoreboard context. Values: National, State, Section, StateDivision, Association, League, DMA; see maxpreps-request-enums for the id kind each context needs.
genderSportYesRequired gender+sport value from maxpreps-sports, lowercased as the site sends it (for example boys,football). Case-insensitive.
excludeTbaDateNoOptional exclude contests whose date is still TBA.
nationalTeamCountNoOptional number of nationally ranked teams to include in a National context scoreboard.

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

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond them: the fixed yesterday/today/tomorrow window, canonical URLs plus contest ids grouped by date, and the index-vs-detail distinction. It says nothing about rate limits, auth or result size, which keeps it from a 5.

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?

Two sentences, front-loaded with the verb and resource, followed by return shape and usage caveat. The middle clause enumerating all seven contexts is somewhat list-heavy but earns its place by scoping the input.

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 an output schema present and annotations covering the safety profile, the description supplies what is missing: that the date window is fixed at yesterday/today/tomorrow, that results are ids plus canonical URLs, and that no date parameter exists. An agent has everything needed to call it and interpret the output correctly.

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%, so every parameter (context, genderSport, level, id, excludeTbaDate, nationalTeamCount) is already documented in the schema. The description restates the context enumeration and the single-context/single-sport/single-level constraint but adds no new syntax or format detail, which matches the baseline of 3 when the schema does the heavy lifting.

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 ('Get MaxPreps scoreboard contest ids by date') and pins the scope to one context, one genderSport and one level. It also explicitly delimits what is returned ('the id index, not the contest detail'), so an agent can distinguish it from contest-detail routes without reading the schema.

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?

Gives a clear use case ('Use the ids to discover which games exist on a date') and a negative scope ('this route returns the id index, not the contest detail'), which steers the agent away from expecting game data. It does not name a specific sibling for the follow-up detail lookup, so it stops short of full alternative routing.

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