Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_swing_path

Retrieve MLB Baseball Savant Swing Path and Attack Angle rows by batter, team, or league, filtered by season, game, swing, date, side, contact, hard-hit, attack zone, and pitcher hand.

Instructions

Get Baseball Savant Swing Path and Attack Angle rows. Returns batter, batting-team, or league Swing Path and Attack Angle rows with the first-party season, game, swing, team, date, side, contact, hard-hit, attack-zone, and pitcher-hand filters. Use mlb_discovery for exact values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoLocal sort field
typeNoRow type
limitNoRows per page (1-500)
offsetNoZero-based row offset
team_idNoOptional MLB team id
bat_sideNoBatter side
date_endNoOptional range end in YYYY-MM-DD
sort_dirNoSort direction
game_typeNoGame type
date_startNoOptional range start in YYYY-MM-DD
min_swingsNoMinimum swing threshold
pitch_handNoPitcher hand
season_endNoLast season; must be >= season_start
attack_zoneNoAttack zone
is_hard_hitNoHard-hit filter
contact_typeNoContact type
season_startNoFirst season
min_group_swingsNoMinimum swings per group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.2/5.0
Behavior2/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. 'Get' implies a safe read, but it discloses nothing about pagination semantics (limit/offset), return shape, auth, or rate limits. The enumerated filter dimensions largely restate what the schema already encodes.

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 sentences, front-loaded with the verb and resource, and the row types and filter scope follow immediately. No wasted words, though the second sentence is a dense run-on list.

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 an 18-parameter tool with no output schema and no annotations, the description covers row types, filter scope, and where to resolve values, which is adequate. It still omits pagination behavior and any indication of what a returned row contains, leaving gaps for a tool this complex.

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 the baseline is 3. The description lists the filter categories (season, game, swing, team, date, side, contact, hard-hit, attack-zone, pitcher-hand), which maps onto the parameters but adds no syntax, defaults, or interaction detail 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?

States a specific verb ('Get') and resource ('Baseball Savant Swing Path and Attack Angle rows'), and names the three row types (batter, batting-team, league). It is clear what the tool does, though it never distinguishes itself from similar mlb_statcast_* siblings like swing_timing or bat_tracking.

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 only guidance is 'Use mlb_discovery for exact values,' which routes the agent to a sibling for enum resolution. There is no explicit when-to-use or when-not-to-use guidance relative to the other Statcast leaderboard tools, so usage is only implied.

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