Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_first_base_receiving

Fetch Baseball Savant First Base Receiving leaderboards by season, team, hand, height, and outcome filters to analyze first baseman and throwing fielder metrics.

Instructions

Get Baseball Savant First Base Receiving leaderboards. Returns first baseman, throwing fielder, fielding team, batting team, or league receiving rows. Includes season/game selections, threshold and group filters, team/date/hand/height/outcome filters, and validated page-local split filters and sorting. Per-play source records are available through mlb-statcast-first-base-receiving-details. 3D trajectory visualizations are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minNoMinimum opportunities
typeNoLeaderboard group
limitNoRows per page, 1-500
offsetNoZero-based row offset
team[]NoMLB team ids
dateEndNoInclusive end date (YYYY-MM-DD)
split[]NoGroup dimensions
minSplitNoMinimum opportunities within each group
season[]NoSeason values
dateStartNoInclusive start date (YYYY-MM-DD)
splitYearNoYear split selector
gameType[]NoGame types
sortColumnNoLocal sort field
sortDirectionNoLocal sort direction
bin_time_X10[]NoTime bins
fielder_3_handNoFirst baseman batting hand
throw_pos_id[]NoThrowing position ids
runners_on_cd[]NoBase occupancy codes
throw_height_code[]NoThrow heights
min_height_in_inchesNoMinimum fielder height, inches
is_hit_into_play_field_outNoField-out flag
throw_location_code_full[]NoThrow outcomes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/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 the return granularity and a scope limitation, and notes split filters are 'validated' and 'page-local', but says nothing about pagination behavior, data freshness, or rate/auth considerations for a 22-parameter query 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?

Purpose is front-loaded in the first sentence, followed by return content, then capabilities and exclusions. Four sentences are appropriately sized for a 22-parameter tool, though the capability list is somewhat dense.

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 high-complexity, 22-parameter leaderboard tool with no output schema and no annotations, the description covers purpose, return rows, capability scope, sibling routing, and an exclusion. The absence of any note on pagination or result volume is the remaining 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%, so each of the 22 parameters is already documented, making 3 the baseline. The description groups them into seasons/games, thresholds, entity filters, and splits/sorting, which adds organizational but little syntactic or semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 First Base Receiving leaderboards') and enumerates the row types returned (first baseman, throwing fielder, fielding team, batting team, league). It explicitly distinguishes itself from the sibling mlb-statcast-first-base-receiving-details, which handles per-play records.

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?

It routes the agent to the correct sibling by noting per-play source records live in mlb-statcast-first-base-receiving-details, and it declares a scope exclusion ('3D trajectory visualizations are not included'). It stops short of explicit when-to-use/when-not statements, but the alternative is named.

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