Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_pitch_arsenal_details

Fetch game-level pitch play data from Baseball Savant's Pitch Arsenal by supplying player ID, pitch type, and season to expand a batter or pitcher row.

Instructions

Get Baseball Savant Pitch Arsenal play details. Returns game-level pitches expanded from one batter or pitcher pitch-arsenal row. Supply player_id, player_type, year, and the row's pitch_type. The upstream's min_ab request parameter is ignored, so it is not exposed. Rows include play_id values used by Baseball Savant's video pages; this endpoint returns play data and identifiers, not video media.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoSeason
limitNoRows per page (1-500)
offsetNoZero-based row offset
player_idYesPositive MLB player id from mlb-statcast-pitch-arsenal
pitch_typeYesPitch type from the selected row
player_typeNoRow type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers two genuinely useful facts: the upstream min_ab parameter is ignored and deliberately unexposed, and the response contains play data and play_id identifiers rather than video media. It does not cover pagination behavior or error cases, keeping it short of a 5.

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?

Four sentences, front-loaded with the purpose and actionable input guidance. Minor redundancy between the opening "Get...play details" and the following "Returns game-level pitches" sentence, but no padding overall.

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 6-parameter, no-output-schema, no-annotation read tool, the description covers purpose, required inputs, a hidden upstream parameter, and the shape of the return (play data plus identifiers, not media). Pagination via limit/offset is left unexplained, which is the only notable gap.

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 each parameter is already documented in the schema, including that player_id comes from mlb-statcast-pitch-arsenal and pitch_type from the selected row. The description restates the required inputs without adding syntax, format, or constraint detail beyond the schema, so a baseline 3 applies.

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 Baseball Savant Pitch Arsenal play details") and clarifies the scope: game-level pitches expanded from a single batter/pitcher pitch-arsenal row. This positions it as a drill-down, which helps distinguish it from the sibling mlb_statcast_pitch_arsenal(s) tools, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "expanded from one batter or pitcher pitch-arsenal row" plus "Supply player_id, player_type, year, and the row's pitch_type" encodes the prerequisite workflow (start from an arsenal row, then drill in). It gives clear context for when to use it but does not name the source tool or state any when-not-to-use conditions.

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