Skip to main content
Glama

nba_homepage_leaders

Read-only

Get NBA homepage leader board. Returns the homepage leader board for one category. This endpoint has no required parameter beyond the league: a LeagueID-only request answers 200 and echoes its whole contract, which is how its parameter names were recovered after an earlier sampled request answered 400. Note its category spelling is the upstream's own — 'Points' and 'Rebounds', not the 'PTS' short form leagueleaders uses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
league_idNoOptional league id; only 00 (NBA) is verified.
game_scopeNoOptional game window; only Season is verified. Defaults to Season.
player_scopeNoOptional player pool; only All Players is verified. Defaults to All Players.
stat_categoryNoOptional leader category; Points or Rebounds are verified. Defaults to Points.
player_or_teamNoOptional subject; only Team is verified. Defaults to Team.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — a LeagueID-only request returns 200 and echoes the full contract — but spends most of its behavioral content on a discovery anecdote ("recovered after an earlier sampled request answered 400") that does not tell the agent how the tool behaves when invoked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first two sentences, which is good. The remaining text is a meandering implementation history about recovering parameter names from 400/200 responses — context that costs the reader attention without changing how the tool is called.

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 an output schema present and full schema description coverage, the description needn't explain return values, and it covers the purpose plus the notable naming quirk. The remaining gap is routing: nothing explains when this is the right leader-board tool versus its many siblings.

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% and every parameter already documents its verified values and defaults, so the schema does the heavy lifting. The category-spelling warning ("Points" and "Rebounds", not "PTS") reinforces a schema fact and is mildly useful as an emphasis, but adds no new meaning beyond the provided fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Get NBA homepage leader board" and clarifies it is scoped to "one category." This is clear, but it never distinguishes itself from plausible siblings such as nba_homepage_v2 or nba_team_stats_leaders, so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase "for one category" hints that stat_category selects the board, but nothing tells an agent why it would pick this over the league-leader or team-stat siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.