Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_player_details

Fetch expanded Statcast player plays for a batter or pitcher, returning game-level pitch and batted-ball rows with matchup, date, event, exit velocity, launch angle, distance, and video availability.

Instructions

Get expanded standard Baseball Savant Statcast player plays. Returns the game-level pitch or batted-ball rows shown when expanding a batter or pitcher row in the standard Statcast leaderboard, including matchup, date, event, exit velocity, launch angle, distance, play id, and video availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoSeason from 2015 through the current season
player_idYesPositive MLB player id from a batter or pitcher row
player_typeNoPlayer row type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return content (matchup, date, event, exit velocity, launch angle, distance, play id, video availability), implying a read-only data fetch, but does not state permissions, rate limits, pagination, or whether results are season-scoped by default.

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?

Two front-loaded sentences that state purpose first, then enumerate returns; every clause is informative. Slight redundancy in 'standard Baseball Savant Statcast ... standard Statcast leaderboard' keeps it short of a 5.

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?

No output schema exists, and the description compensates by enumerating the returned fields, which is exactly what an agent needs for a data-retrieval tool. Missing only default/scope behavior for the optional year and player_type parameters, so it is nearly complete.

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%, and the schema already documents year, player_id, and the batter/pitcher enum, so the baseline is 3. The description adds only the loose mapping of 'batter or pitcher row' to player_type and no new syntax, defaults, or format guidance.

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 (Get) and resource (expanded Statcast player plays), and the second sentence clarifies exactly what the output rows represent — game-level pitch/batted-ball rows from expanding a batter/pitcher leaderboard row. It is clearly distinguishable in kind from summary siblings like mlb_statcast (leaderboard) and matches the '*_details' family pattern, though it does not name which sibling to prefer.

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 frames the tool as the expansion of a batter/pitcher row in the standard Statcast leaderboard, which implies when it applies, but it gives no explicit when-to-use versus alternatives (e.g., mlb_statcast_batted_ball or mlb_statcast_home_runs_details) and states no prerequisites or required parent context beyond the schema.

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