Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_team_stats

Get MLB team season statistics by team ID and stat group, with optional season, stat type, and date range filters.

Instructions

Get MLB team season statistics. Returns one MLB team's statistics. team_id and group (hitting, pitching, fielding, catching, running, game, team or streak) are required. season defaults to the current year and stat_type to season. Other stat_type values cover splits and logs. Use start_date with end_date for date ranges.

Input Schema

NameRequiredDescriptionDefault
groupYesStatistics group
seasonNoFour-digit season
team_idYesNumeric MLB team id
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

A3.5/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 burden. "Get" and "Returns one MLB team's statistics" imply a safe read, and defaults/date-range pairing are disclosed, but there is no statement about auth requirements, rate limits, or response shape. Adequate but thin for a zero-annotation tool.

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?

Front-loads purpose before parameters and stays compact. The first two sentences are partly redundant ("Get MLB team season statistics" / "Returns one MLB team's statistics"), but the rest earns its place with concrete defaults and constraints.

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 nine-parameter, no-annotation, no-output-schema tool, the description covers the required parameters, defaults, and the date-range pairing an agent needs to invoke it correctly. Remaining params (game_type, opponent_* ) are left to the schema, which is acceptable given 100% coverage.

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%, so the schema already documents all nine parameters and the enums. The description mostly restates this (group values, defaults) but does add the relationship "Use start_date with end_date" and the note that other stat_type values cover splits and logs, which is marginally beyond 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?

The description states a specific verb and resource ("Get MLB team season statistics") and scopes it to "one MLB team's statistics," which separates it from the sibling mlb_player_stats and mlb_league_stats. It does not name those siblings explicitly, so the differentiation relies on the agent inferring scope from the word "team."

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?

It gives operational constraints (required team_id/group, season and stat_type defaults, start_date/end_date pairing) but never says when to prefer this tool over mlb_player_stats or mlb_league_stats. Usage is implied by the resource scope rather than stated as an explicit condition.

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