Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_player_stats

Fetch an MLB player's season statistics by player ID and stat group, with optional season and game type filters.

Instructions

Get MLB player season statistics. Returns one player's MLB season statistics. The group enum accepts every value returned by mlb_discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric MLB player id
groupYesStat group
seasonNoFour-digit season; defaults to current year
end_dateNoEnd date for byDateRange stat types; requires start_date
game_typeNoMLB game type
stat_typeNoStats API stat type; defaults to season
start_dateNoStart date for byDateRange stat types; requires end_date
opponent_team_idNoRequired by vsTeam stat types
opponent_player_idNoRequired by vsPlayer stat types

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.17.7
    • 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"
+}
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / group / enum
      Added value: +[
+  "hitting",
+  "pitching",
+  "fielding"
+]
  3. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses almost nothing beyond the basic read: no note on read-only safety, auth, rate limits, or how the 60+ stat_type values change the response shape. It does flag that the group value comes from mlb_discovery, which is a small but real addition.

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 first two sentences say essentially the same thing ('Get MLB player season statistics' / 'Returns one player's MLB season statistics'), which is redundant. The distinctive group-ml b_discovery note is last when it would be better 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?

Against 9 parameters, 3 enums, no annotations, and no output schema, the description is far too thin. It omits the behaviors of the large stat_type enum, the start_date/end_date and opponent_* conditional requirements, and what is actually returned, leaving significant complexity undocumented.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema by stating the group enum accepts every value returned by mlb_discovery, which links the parameter to another tool. It stops short of explaining the season/date/stat_type interactions, hence not a 5.

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 player season statistics') plus scope ('one player's'), which is clearer than the tool name alone. However, it never distinguishes itself from siblings like mlb_player, mlb_prospect_stats, mlb_team_stats, or mlb_league_stats, so an agent must still infer the boundary.

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 when-to-use or when-not-to-use guidance and no comparison to alternative player-stat tools. The lone hint ('The group enum accepts every value returned by mlb_discovery') is a parameter/interop note rather than routing advice, so an agent gets little help choosing this tool.

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