Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

mlb: Get league leaders

mlb_get_league_leaders
Read-onlyIdempotent

Retrieve MLB league stat leaders for categories such as home runs, batting average, ERA, and strikeouts, filtered by season.

Instructions

Get league stat leaders for categories like home runs, batting average, ERA, strikeouts, etc.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "leaderCategories": "<leaderCategories>"
    },
    "name": "mlb_get_league_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
seasonNoSeason year (e.g. 2024)
sportIdNoSport ID (1=MLB)
leaderCategoriesYesStat category: "homeRuns", "battingAverage", "earnedRunAverage", "strikeouts", "wins", "saves", "stolenBases", etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is clear. The description adds no behavioral context beyond that, such as rate limits, authentication needs, pagination, or result-count behavior.

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 a single front-loaded sentence with no wasted words. It immediately states the action and the kind of resource returned.

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?

For a simple read-only retrieval tool with complete parameter descriptions and clear safety annotations, the description is largely sufficient. The main gap is that it does not describe the shape of the leaderboard results, but that is a minor omission for this endpoint.

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 description coverage is 100%, so the baseline is 3. The description restates category examples for leaderCategories, but adds no extra parameter meaning for fields, season, or sportId beyond what the schema already documents.

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?

The description states a specific verb and resource: "Get league stat leaders." It gives useful category examples and distinguishes league leaders from player-specific stats by implication, but it does not explicitly contrast itself with siblings such as mlb_get_player_stats or nhl_get_stat_leaders.

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?

The description explains what the tool returns but offers no guidance on when to use it versus alternatives. There is no mention of prerequisites, season defaults, or when another sibling tool would be more appropriate.

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

Deploy Server

Other Tools