mlb-api-mcp

get_mlb_sabermetrics

Retrieve sabermetric statistics like WAR, wOBA, and wRC+ for MLB players by season to analyze advanced baseball performance metrics for hitting or pitching groups.

Instructions

Get sabermetric statistics (including WAR) for multiple players for a specific season.

Args: player_ids (str): Comma-separated list of player IDs. season (int): Season year. stat_name (Optional[str]): Specific sabermetric stat to extract (e.g., 'war', 'woba', 'wRc'). group (str): Stat group ('hitting' or 'pitching').

Returns: dict: Sabermetric statistics.

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": {
      "player_ids": "<player_ids>",
      "season": "<season>"
    },
    "name": "get_mlb_sabermetrics"
  }
}

Input Schema

Name	Required	Default
`player_ids`	Yes
`season`	Yes
`stat_name`	No
`group`	No	hitting

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.0Jan 3, 2026
- removedInput schema / properties / group / title
```
Removed value: -"Group"
```
- removedInput schema / properties / player_ids / title
```
Removed value: -"Player Ids"
```
- removedInput schema / properties / season / title
```
Removed value: -"Season"
```
- removedInput schema / properties / stat_name / title
```
Removed value: -"Stat Name"
```
First observedAug 15, 2025

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but lacks critical behavioral details: whether it's read-only or mutative, rate limits, authentication needs, error handling, or what happens with invalid inputs. The description doesn't contradict annotations (none exist), but provides minimal behavioral context.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Returns sections are structured clearly. While efficient, the 'Returns' section could be slightly more informative given the output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters, no annotations, but has output schema), the description is partially complete. It covers parameters well but lacks behavioral context and usage differentiation from siblings. The output schema reduces need to explain return values, but more guidance on when to use this specific tool would improve completeness.

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?

With 0% schema description coverage, the description compensates well by explaining all 4 parameters in the Args section. It clarifies that player_ids is 'comma-separated,' season is a 'year,' stat_name is 'optional' with examples, and group has two possible values. This adds significant meaning beyond the bare schema types.

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's purpose: 'Get sabermetric statistics (including WAR) for multiple players for a specific season.' It specifies the verb ('Get'), resource ('sabermetric statistics'), scope ('multiple players', 'specific season'), and distinguishes from siblings by focusing on sabermetrics rather than awards, boxscores, or other MLB data.

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 by mentioning 'multiple players' and 'specific season,' but doesn't explicitly state when to use this tool versus alternatives like 'get_multiple_mlb_player_stats' or 'get_statcast_batter.' No exclusions or prerequisites are provided, leaving usage guidance incomplete.

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