Nba

Get Teams

get_teams

Read-onlyIdempotent

Get all 30 NBA teams with full names, abbreviations, conference, and division. Use to find team info or prepare for get_games queries. 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": {},
    "name": "get_teams"
  }
}

Input Schema

Name	Required	Description	Default
`_apiKey`	Yes	BallDontLie API key (free tier: https://www.balldontlie.io/)

Output Schema

Name	Required	Description	Default
`teams`	Yes	List of all NBA teams
`total`	Yes	Total number of NBA teams

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-nba-api-key"
-  }
-]New value: +[
+  {}
+]

Changed1 schema field changedJul 29, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-nba-api-key"
+  }
+]

Changed1 schema field changedJul 29, 2026
- removedInput schema / examples
```
Removed value: -[
-  {}
-]
```

Changed2 schema fields changedMay 10, 2026

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "BallDontLie API key (free tier: https://www.balldontlie.io/)",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "_apiKey"
+]
```

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "teams": {
+      "description": "List of all NBA teams",
+      "items": {
+        "properties": {
+          "abbreviation": {
+            "description": "Team abbreviation",
+            "type": "string"
+          },
+          "city": {
+            "description": "Team city",
+            "type": "string"
+          },
+          "conference": {
+            "description": "Conference (East/West)",
+            "type": "string"
+          },
+          "division": {
+            "description": "Division name",
+            "type": "string"
+          },
+          "full_name": {
+            "description": "Full team name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Team ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Team name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of NBA teams",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "teams"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds the requirement for a free API key, which is a behavioral constraint not in annotations. No contradictions.

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, front-loaded with the core purpose and output details. Every sentence adds value, no wasted words.

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?

Given the simple nature (list tool with one parameter) and presence of output schema, the description fully covers purpose, required setup, and typical use case.

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 coverage is 100% with _apiKey documented. The description mentions the API key but adds no additional semantics beyond the schema. Baseline score of 3 is appropriate.

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?

The description clearly states the tool gets all 30 NBA teams with specific attributes (names, abbreviations, conference, division). It distinguishes from sibling tools like get_games and get_player by specifying the resource and scope.

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?

Explicitly says 'Use to find team info or prepare for get_games queries', providing clear usage context. Lacks explicit when-not or alternatives, but the guidance is sufficient.

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.