Skip to main content
Glama

Nba

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesBallDontLie API key (free tier: https://www.balldontlie.io/)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamsYesList of all NBA teams
totalYesTotal number of NBA teams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-nba-api-key"
+  }
+]
  2. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
-  {}
-]
  3. Changed2 schema fields changed
    • addedInput schema / properties / _apiKey
      Added value: +{
+  "description": "BallDontLie API key (free tier: https://www.balldontlie.io/)",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "_apiKey"
+]
  4. Changed1 schema field changed
    • 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"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds the API key requirement and indicates the static nature of teams. 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, no redundancy, front-loaded with action and key details. Every sentence earns its place.

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?

Given the simplicity (1 param, output schema exists), the description covers purpose, usage, and auth. Complete enough for an agent to select and invoke correctly.

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 a clear description for the _apiKey parameter. The description repeats 'Requires a free BallDontLie API key' but adds no new semantic detail beyond 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 explicitly states 'Get all 30 NBA teams with full names, abbreviations, conference, and division,' providing a specific verb and resource. It clearly distinguishes from sibling tools like get_games and search_players.

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?

Description advises 'Use to find team info or prepare for get_games queries,' giving clear context. It also specifies the API key requirement. Missing explicit exclusions but sufficient for this simple tool.

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