Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_swing_timing_details

Expand per-swing detail arrays for a batter or pitcher Swing Timing row using its unique row_id and matching split filters, so you can map split values to upstream detail queries.

Instructions

Get Baseball Savant Swing Timing player details. Returns the four anonymous per-swing detail arrays expanded from a batter or pitcher Swing Timing row. Pass the row_id uniqueId from mlb-statcast-swing-timing and repeat its type and table filters so split values can be mapped to the upstream detail query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesPlayer row type
flagsNoPositive swing timing flags
teamsNoMLB team ids
countsNoBall-strike counts
row_idYesUnique row id from mlb-statcast-swing-timing, including any selected split values
splitsNoSplit dimensions
seasonsNoSeason filters
bat_sideNoBatter side
date_endNoFilter end date in YYYY-MM-DD format
min_splitNoMinimum group swings
not_flagsNoExcluded swing timing flags
date_startNoFilter start date in YYYY-MM-DD format
game_typesNoGame-type filters
min_swingsNoMinimum swings
pitch_handNoPitcher hand
split_yearNoInclude year in the row grouping
attack_zoneNoAttack zone
pitch_typesNoPitch type codes
contact_typeNoContact type
swing_timing_xNoTied-up/flail axis values
swing_timing_yNoEarly/late axis values
swing_timing_zNoOver/under axis values

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 burden. It discloses that the return consists of 'four anonymous per-swing detail arrays' and that filters must be repeated for split mapping, which is useful. However, it does not say what the anonymous arrays contain, whether results are paginated, or what permissions/rate limits apply, leaving meaningful gaps for a detail 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?

Three sentences, front-loaded with what the tool returns and then the prerequisite row_id. It is efficient and avoids restating schema details, though the second sentence is dense and could be split for readability.

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

Completeness3/5

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

For a 22-parameter tool with no output schema and no annotations, the description gives the essential prerequisite (row_id) and notes the return shape is four anonymous arrays. It still leaves gaps on the nature of those arrays, how filters must match upstream calls exactly, and any error behavior, which an agent would need to call correctly.

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 every parameter is already documented in the schema; the baseline is 3. The description adds a small amount of meaning by noting that type and table filters must be repeated so split values map to the upstream detail query, but most parameter semantics are already in 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: retrieves per-swing detail arrays expanded from a Swing Timing row, and names the source (Baseball Savant Swing Timing). It distinguishes itself from the sibling mlb_statcast_swing_timing by describing itself as the detail expansion of a row, though the phrasing 'expanded from a batter or pitcher Swing Timing row' is slightly terse.

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?

Explicitly says to pass the row_id from mlb-statcast-swing-timing and to repeat its type and table filters, which is concrete usage guidance tying this tool to a prerequisite call. It does not state when NOT to use it, but the prerequisite dependency is clearly conveyed.

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