Nba

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "season": 2024
    },
    "name": "get_games"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of results to return (default: 25, max: 100)
`season`	Yes	Season start year (e.g., 2024 for the 2024-25 season)
`_apiKey`	Yes	BallDontLie API key (free tier: https://www.balldontlie.io/)

Output Schema

Name	Required	Description
`games`	Yes	List of games
`total`	Yes	Total games in season
`season`	Yes	Season start year
`returned`	Yes	Number of games returned in this response

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

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"
+}

Changed2 schema fields changedMay 13, 2026

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

Changed2 schema fields changedMay 10, 2026

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"
+]

Changed1 schema field changedMay 8, 2026

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"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "season": 2024
+  },
+  {
+    "limit": 50,
+    "season": 2023
+  }
+]

First observedApr 22, 2026

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 tools Inspect

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.

Get Games

Example tool call

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources