Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast

Retrieve Baseball Savant Statcast leaderboard data for batters, pitchers, and teams with filters for season, position, and metrics.

Instructions

Get Baseball Savant Statcast leaderboard data. Returns the standard anonymous Baseball Savant Statcast leaderboard for batters, pitchers, teams, or pitcher teams. Supports the page's season, team, batter position, minimum batted-ball event, and sortable metric filters, plus local pagination. Use mlb_discovery for exact filter sets. Other Baseball Savant leaderboard pages are listed there but are not represented by this route.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field
typeNoLeaderboard row type
yearNoSeason; current season back 11 seasons
limitNoRows per page (1-500)
offsetNoZero-based row offset
min_bbeNoMinimum batted-ball event threshold
team_idNoOptional MLB team id from mlb_teams
positionNoBatter position
sort_dirNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden, and it does disclose meaningful traits: the leaderboard is 'anonymous' (no auth needed) and pagination is 'local' rather than server-side. It also bounds the route's coverage. It stops short of describing return fields or rate limits, but for a read-only leaderboard call this is solid added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, front-loaded with what the tool returns before the routing guidance. The filter list is enumerative rather than repetitive, and the alternative-route pointer comes last as a natural fallback.

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 9-parameter, all-optional read tool with no output schema or annotations, the description covers purpose, scope limits, anonymity, and pagination. Defaults for sort/sort_dir/limit are left to the schema, which is acceptable given 100% coverage, though a note on default ordering would make it fully 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% with clear per-parameter descriptions and enums, so the schema already documents all 9 filters. The description's enumeration of filter groups (season, team, position, min batted-ball event, sortable metric) mirrors the schema without adding ranges, defaults, or syntax beyond it, so baseline 3 applies.

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?

Specific verb+resource ('Get Baseball Savant Statcast leaderboard data') with the row granularity spelled out (batters, pitchers, teams, pitcher teams). It also explicitly differentiates the route from other Savant leaderboard pages, so an agent can distinguish it from siblings like mlb_statcast_expected and mlb_discovery.

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?

Names the alternative route ('Use mlb_discovery for exact filter sets') and warns that other Savant leaderboard pages are not covered by this route. It gives clear context for selection but does not state a full when-not-to-use rule for the filters this route does handle.

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