Skip to main content
Glama

Nba

by io.github.pipeworx-io

Get Games

get_games
Read-onlyIdempotent

Get NBA games for a season (e.g., 2023, 2024). Returns game date, status, matchup teams, and final or live scores. Requires a free BallDontLie API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (default: 25, max: 100)
seasonYesSeason start year (e.g., 2024 for the 2024-25 season)
_apiKeyYesBallDontLie API key (free tier: https://www.balldontlie.io/)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gamesYesList of games
totalYesTotal games in season
seasonYesSeason start year
returnedYesNumber of games returned in this response

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "season": 2024
+  },
+  {
+    "limit": 50,
+    "season": 2023
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "games": {
+      "description": "List of games",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Game date",
+            "type": "string"
+          },
+          "home_score": {
+            "description": "Home team score",
+            "type": "number"
+          },
+          "home_team": {
+            "description": "Home team full name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Game ID",
+            "type": "number"
+          },
+          "period": {
+            "description": "Current period/quarter",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "postseason": {
+            "description": "Whether game is in postseason",
+            "type": "boolean"
+          },
+          "season": {
+            "description": "Season year",
+            "type": "number"
+          },
+          "status": {
+            "description": "Game status (Final, In Progress, etc.)",
+            "type": "string"
+          },
+          "time": {
+            "description": "Game time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "visitor_score": {
+            "description": "Visiting team score",
+            "type": "number"
+          },
+          "visitor_team": {
+            "description": "Visiting team full name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of games returned in this response",
+      "type": "number"
+    },
+    "season": {
+      "description": "Season start year",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total games in season",
+      "type": "number"
+    }
+  },
+  "required": [
+    "season",
+    "total",
+    "returned",
+    "games"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "season": 2024
-  },
-  {
-    "limit": 50,
-    "season": 2023
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "games": {
-      "description": "List of games",
-      "items": {
-        "properties": {
-          "date": {
-            "description": "Game date",
-            "type": "string"
-          },
-          "home_score": {
-            "description": "Home team score",
-            "type": "number"
-          },
-          "home_team": {
-            "description": "Home team full name",
-            "type": "string"
-          },
-          "id": {
-            "description": "Game ID",
-            "type": "number"
-          },
-          "period": {
-            "description": "Current period/quarter",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "postseason": {
-            "description": "Whether game is in postseason",
-            "type": "boolean"
-          },
-          "season": {
-            "description": "Season year",
-            "type": "number"
-          },
-          "status": {
-            "description": "Game status (Final, In Progress, etc.)",
-            "type": "string"
-          },
-          "time": {
-            "description": "Game time",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "visitor_score": {
-            "description": "Visiting team score",
-            "type": "number"
-          },
-          "visitor_team": {
-            "description": "Visiting team full name",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "returned": {
-      "description": "Number of games returned in this response",
-      "type": "number"
-    },
-    "season": {
-      "description": "Season start year",
-      "type": "number"
-    },
-    "total": {
-      "description": "Total games in season",
-      "type": "number"
-    }
-  },
-  "required": [
-    "season",
-    "total",
-    "returned",
-    "games"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changed
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "BallDontLie API key (free tier: https://www.balldontlie.io/)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "season"
-]New value: +[
+  "season",
+  "_apiKey"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "games": {
+      "description": "List of games",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Game date",
+            "type": "string"
+          },
+          "home_score": {
+            "description": "Home team score",
+            "type": "number"
+          },
+          "home_team": {
+            "description": "Home team full name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Game ID",
+            "type": "number"
+          },
+          "period": {
+            "description": "Current period/quarter",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "postseason": {
+            "description": "Whether game is in postseason",
+            "type": "boolean"
+          },
+          "season": {
+            "description": "Season year",
+            "type": "number"
+          },
+          "status": {
+            "description": "Game status (Final, In Progress, etc.)",
+            "type": "string"
+          },
+          "time": {
+            "description": "Game time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "visitor_score": {
+            "description": "Visiting team score",
+            "type": "number"
+          },
+          "visitor_team": {
+            "description": "Visiting team full name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of games returned in this response",
+      "type": "number"
+    },
+    "season": {
+      "description": "Season start year",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total games in season",
+      "type": "number"
+    }
+  },
+  "required": [
+    "season",
+    "total",
+    "returned",
+    "games"
+  ],
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "season": 2024
+  },
+  {
+    "limit": 50,
+    "season": 2023
+  }
+]
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. Description adds context about return fields and API key requirement, but does not cover pagination or error handling.

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?

Two sentences, no wasted words, effectively communicates purpose and prerequisites.

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 output schema present, description adequately explains return data. Missing details on pagination or limit behavior, but acceptable for a simple GET tool.

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?

Input schema covers all parameters with descriptions. Description does not add new meaning beyond what is already in the schema.

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?

Description clearly states it gets NBA games for a season, returning specific fields. Distinguishes from sibling tools like get_player and get_teams by focusing on games.

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?

Implies usage for retrieving NBA game data but does not mention when to use this versus alternatives like search_players or other game-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nba toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Many tools serve overlapping purposes: ask_pipeworx, ask_pipeworx_grounded, deep_research all provide factual lookups with similar boundaries. NBA-specific tools are mixed with generic Pipeworx utilities, making it hard for an agent to distinguish when to use which.

Naming Consistency2/5

Tool names mix conventions: snake_case (ai_visibility_check), camelCase (generate_llms_txt), and inconsistent verb usage (ask_pipeworx vs. search_players). No clear pattern emerges across the set.

Tool Count2/5

With 34 tools, the server is overpopulated, especially given its 'Nba' focus. Many tools (e.g., remember, forget, list_subscriptions) are generic utilities unrelated to NBA data, inflating the count beyond a coherent scope.

Completeness2/5

For an NBA server, tools are severely incomplete: missing player stats, team stats, season standings, and live game details. While the Pipeworx data tools are extensive, they diverge from the server's apparent purpose, leaving clear gaps.

Resources