Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

mlb_team_stats

Retrieve MLB team season statistics by team ID and stat group, including hitting, pitching, fielding, running, and game splits for a chosen season.

Instructions

Get MLB team season statistics. Returns one team's season statistics. Group accepts every value returned by mlb_discovery.

Input Schema

TableJSON Schema

Name	Required	Description
`group`	Yes	Statistics group
`season`	No	Four-digit season
`team_id`	Yes	Numeric MLB team id
`end_date`	No	End date for byDateRange stat types; requires start_date
`game_type`	No	MLB game type
`stat_type`	No	Stats API stat type; defaults to season
`start_date`	No	Start date for byDateRange stat types; requires end_date
`opponent_team_id`	No	Required by vsTeam stat types
`opponent_player_id`	No	Required by vsPlayer stat types

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.17.7Oct 1, 2026

addedInput schema / properties / end_date

Added value: +{
+  "description": "End date for byDateRange stat types; requires start_date",
+  "type": "string"
+}

addedInput schema / properties / game_type

Added value: +{
+  "description": "MLB game type",
+  "enum": [
+    "S",
+    "R",
+    "F",
+    "D",
+    "L",
+    "W",
+    "C",
+    "P",
+    "A",
+    "I",
+    "E"
+  ],
+  "type": "string"
+}

changedInput schema / properties / group / enum

Previous value: -[
-  "hitting",
-  "pitching",
-  "fielding"
-]New value: +[
+  "hitting",
+  "pitching",
+  "fielding",
+  "catching",
+  "running",
+  "game",
+  "team",
+  "streak"
+]

addedInput schema / properties / opponent_player_id

Added value: +{
+  "description": "Required by vsPlayer stat types",
+  "type": "string"
+}

addedInput schema / properties / opponent_team_id

Added value: +{
+  "description": "Required by vsTeam stat types",
+  "type": "string"
+}

addedInput schema / properties / start_date

Added value: +{
+  "description": "Start date for byDateRange stat types; requires end_date",
+  "type": "string"
+}

addedInput schema / properties / stat_type

Added value: +{
+  "description": "Stats API stat type; defaults to season",
+  "enum": [
+    "projected",
+    "projectedRos",
+    "yearByYear",
+    "yearByYearAdvanced",
+    "yearByYearPlayoffs",
+    "season",
+    "standard",
+    "advanced",
+    "career",
+    "careerRegularSeason",
+    "careerAdvanced",
+    "seasonAdvanced",
+    "careerStatSplits",
+    "careerPlayoffs",
+    "gameLog",
+    "playLog",
+    "pitchLog",
+    "pitchArsenal",
+    "outsAboveAverage",
+    "expectedStatistics",
+    "sabermetrics",
+    "sprayChart",
+    "tracking",
+    "vsPlayer",
+    "vsPlayerTotal",
+    "vsPlayer5Y",
+    "vsTeam",
+    "vsTeam5Y",
+    "vsTeamTotal",
+    "lastXGames",
+    "byDateRange",
+    "byDateRangeAdvanced",
+    "byMonth",
+    "byMonthPlayoffs",
+    "byDayOfWeek",
+    "byDayOfWeekPlayoffs",
+    "homeAndAway",
+    "homeAndAwayPlayoffs",
+    "winLoss",
+    "winLossPlayoffs",
+    "rankings",
+    "rankingsByYear",
+    "statsSingleSeason",
+    "statsSingleSeasonAdvanced",
+    "hotColdZones",
+    "availableStats",
+    "opponentsFaced",
+    "gameTypeStats",
+    "firstYearStats",
+    "lastYearStats",
+    "statSplits",
+    "statSplitsAdvanced",
+    "atGameStart",
+    "vsOpponents",
+    "sabermetricsMultiTeam",
+    "projected_Zips",
+    "projected_ZipsRos",
+    "projected_Zips2YR",
+    "projected_Zips3YR"
+  ],
+  "type": "string"
+}

Changed1 schema field changedv1.17.5Sep 26, 2026
- addedInput schema / properties / group / enum
```
Added value: +[
+  "hitting",
+  "pitching",
+  "fielding"
+]
```
AddedAug 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the call returns a single team's stats (not a list) and that group values are derived from another tool, but it says nothing about stat_type defaults beyond the schema, permissions, or result size. Minimal but not misleading.

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?

Sentence 1 and sentence 2 restate the same fact ('MLB team season statistics' / 'one team's season statistics'), which is redundant. Only the third sentence adds information, and it is buried at the end rather than front-loaded.

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

Completeness2/5

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

With nine parameters, three enums, no output schema, and no annotations, the description is too thin. It never explains how stat_type interacts with season, start_date/end_date, or opponent_team_id / opponent_player_id, which is the real complexity an agent must navigate before calling this tool.

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 adds one genuinely non-schema detail for group (values come from mlb_discovery), but leaves the other eight parameters—stat_type, season, date-range, and opponent params—entirely to the schema.

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 MLB team season statistics') and clarifies the return shape ('one team's season statistics'). It implicitly distinguishes from the mlb_player_stats / mlb_league_stats siblings via 'team' but never names them, so the differentiation rests on the reader's inference.

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 third sentence links the group parameter to mlb_discovery, which is a useful routing hint, but there is no explicit when-to-use guidance relative to mlb_player_stats or mlb_league_stats, and no statement of when this tool is the wrong choice.

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

Deploy Server

mlb_team_stats

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools