Skip to main content
Glama
stevenyuser

NBA MCP Server

by stevenyuser

get_today_scoreboard

Retrieve live NBA game scores, team information, and game statuses for today's matchups. This tool provides current basketball data to track ongoing games and results.

Instructions

Get the current NBA scoreboard for today's games. The NBA scoreboard provides live data for games, including scores, game statuses, and team information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches and returns the current NBA scoreboard for today's games using the nba_api scoreboard endpoint.
    def get_today_scoreboard() -> dict:
        """
        Get the current NBA scoreboard for today's games. The NBA scoreboard provides 
        live data for games, including scores, game statuses, and team information.
        """
        try:
            board = scoreboard.ScoreBoard()
            print(board.games)
            if not board.games or not board.games.get_dict():
               raise ValueError("No games found for today.")
            return board.games.get_dict()
        except Exception as e:
            return {"error": str(e)}
  • server.py:139-139 (registration)
    Registers the get_today_scoreboard tool using the FastMCP @mcp.tool decorator.
    @mcp.tool
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'live data' and 'game statuses', which hints at real-time updates, but does not disclose behavioral traits such as rate limits, data freshness, authentication needs, or error handling. The description adds minimal context beyond the basic purpose.

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?

The description is two concise sentences that are front-loaded with the core purpose and efficiently elaborate on the data provided. Every sentence adds value without redundancy, making it easy to parse.

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 tool's low complexity (0 parameters, simple read operation) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers what data is fetched and its temporal scope, though it lacks details on behavioral aspects like data latency or limitations.

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?

There are 0 parameters, and schema description coverage is 100% (empty schema). The description appropriately does not discuss parameters, focusing instead on the tool's output scope ('today's games', 'live data'). This aligns with the baseline of 4 for zero parameters.

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 specific action ('Get'), resource ('NBA scoreboard'), and temporal scope ('today's games'). It distinguishes from siblings like get_league_team_standings (standings) and get_live_game_boxscore (detailed boxscores) by focusing on the current day's game overview with scores and statuses.

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?

The description implies usage context ('today's games', 'live data') but does not explicitly state when to use this tool versus alternatives like get_team_game_log (historical logs) or get_live_game_play_by_play (detailed play data). No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stevenyuser/nba_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server