Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

maxpreps_team_schedule

Read-only

Get MaxPreps team schedule and results. Returns one team season's full schedule with results: each contest's date, site, state, per-team scores (b1..b30), result, home/away type, forfeit/TBA flags, contest state (Pregame, ContestInProgress, Boxscore, ScoreNotReported) and the derived fields the site renders (title, contest alias, canonical URL, overtime, tournament and bracket identity).

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": {
      "teamId": "<teamId>",
      "sportSeasonId": "<sportSeasonId>"
    },
    "name": "maxpreps_team_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesRequired team id from maxpreps-school-search or maxpreps-team.
sportSeasonIdYesRequired sport-season id for that exact team and level.

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

B3.2/5.0
Behavior3/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 useful return detail, including contest states (Pregame, ContestInProgress, Boxscore, ScoreNotReported), forfeit/TBA flags, and derived fields, but it does not describe pagination, rate limits, or error behavior. With an output schema present, much of the return enumeration is redundant.

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?

The definition is a single front-loaded sentence: purpose first, then return contents. It is dense but has no filler, though the long field enumeration is somewhat heavy given that an output schema already exists.

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 two-parameter read-only tool with annotations and an output schema, the definition gives enough context to call it correctly. The remaining gap is routing guidance versus sibling schedule and contest tools, which would make it 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 both parameters already have clear descriptions including where teamId comes from. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'Get MaxPreps team schedule and results', and scopes it to one team season's full schedule with results. An agent can distinguish it from a next-contest tool by the 'full schedule' framing, but the definition never names a sibling alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description implies usage by saying it returns a full season schedule rather than a single contest, but it never names an alternative (e.g., next-contest or scoreboard tools) or states prerequisites.

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