Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nbl_schedule

Read-onlyIdempotent

Fetch the complete NBL season schedule and results, including match times, scores, venues, and team details. Sort by start_time for chronological order.

Instructions

Every match for one season: start_time, round, status, home/away scores, attendance, venue, match_slug/title, and home_team/away_team (id, name, team_code, logo, colour). id is the match id for nbl_match_boxscore and nbl_match_playbyplay. Rows are NOT in date order, so sort by start_time. seasonType=all for the whole season.

Returns: {type, count, data:[{id, external_id, start_time, round, match_type, status:'SCHEDULED'|'CONFIRMED'|'DRAFT', match_status:'scheduled'|'complete'|'draft', home_score, away_score, attendance, match_slug, match_title, play_by_play, venue:{name}, home_team:{id, name, team_code, team_logo, color_primary}, away_team:{…}}]} — a finished game is status CONFIRMED / match_status complete. play_by_play is an id string once a game has play-by-play and null before; it is not a flag. Scores are STRINGS ('86', not 86) and null until a game is played.

Example: Full NBL27 schedule and results {"year": 2026, "seasonType": "all"}

Auth: none needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesSeason START year — 2025 = NBL26 (current 2025-26 season), 2026 = NBL27. Required — part of the URL path.
limitNoRows to return. 400 covers a whole season in one call; the feed's own default is 100, which silently drops the rest.
offsetNoRows to skip, for paging past `limit`.
seasonTypeNoPhase to list (default all). The NBL Blitz pre-season tournament is filed under in_season.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.33.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 400,
+  "description": "Rows to return. 400 covers a whole season in one call; the feed's own default is 100, which silently drops the rest.",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": null,
+  "description": "Rows to skip, for paging past `limit`.",
+  "type": "integer"
+}
    • changedInput schema / properties / seasonType / description
      Previous value: -"Phase to list (default all)."New value: +"Phase to list (default all). The NBL Blitz pre-season tournament is filed under in_season."
  2. Changed3 schema fields changedv0.24.0
    • addedInput schema / properties / seasonType / description
      Added value: +"Phase to list (default all)."
    • addedInput schema / properties / seasonType / enum
      Added value: +[
+  "all",
+  "regular",
+  "in_season",
+  "preseason",
+  "finals"
+]
    • addedInput schema / properties / year / description
      Added value: +"Season START year — 2025 = NBL26 (current 2025-26 season), 2026 = NBL27. Required — part of the URL path."
  3. Addedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: warns rows are NOT in date order, that scores are STRINGS and null until played, that play_by_play is an id string not a flag, that CONFIRMED/complete marks a finished game, that the API default limit is 100 and silently truncates, and that no auth is needed.

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?

Dense but front-loaded: purpose, field list, caveats, then the return shape. Nearly every sentence carries operational detail; the return-shape block slightly duplicates the field enumeration, costing a little crispness.

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 no output schema present, the description fully specifies the response envelope and per-row shape, documents all four params at 100% coverage, and warns about paging truncation and unordered rows. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the required year is a season START year (2025=NBL26), the sort-by-start_time caveat, and seasonType=all semantics that the enum alone doesn't convey.

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?

Opens with a specific verb+resource+scope ('Every match for one season') and enumerates the exact fields returned. It also names the two sibling tools (nbl_match_boxscore, nbl_match_playbyplay) that the returned `id` feeds, so an agent can distinguish it from nbl_next_matches/nbl_match_outcomes without opening a 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 clear context for selection ('seasonType=all for the whole season', id feeds boxscore/playbyplay) plus an example call. It does not explicitly contrast with the obviously adjacent sibling nbl_next_matches, so the when-not alternative is left implicit.

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