Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_expected

Retrieve Baseball Savant expected statistics leaderboards for batters, pitchers, and teams, with filters for season, team, position, and qualifiers, plus sorting and pagination.

Instructions

Get Baseball Savant Expected Statistics. Returns the separate Expected Statistics leaderboard with batter, pitcher, and team views; season, team, batter-position, BIP/PA qualifier and threshold filters; local metric sorting; and pagination. League-average values are returned separately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field
typeNoLeaderboard view
yearNoSeason from 2015 through the current season
limitNoRows per page (1-500)
offsetNoZero-based row offset
minimumNoMinimum BIP/PA threshold
team_idNoOptional MLB team id from mlb_teams
positionNoBatter position; only supported for type=batter
sort_dirNoSort direction
filter_typeNoMinimum qualifier type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.5/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 shape well (separate leaderboard, views, filtering, sorting, pagination, separate league averages), but does not state read-only operation, auth requirements, or anything about rate limits or result stability.

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?

A single tight paragraph that front-loads the identity and then enumerates views, filters, sorting, and pagination. No filler sentences, though it packs several clauses into one stream that could be cleaner.

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 10-parameter read tool with no output schema and no annotations, the description covers the return structure, the filter set, sorting, pagination, and the separate league averages, which is most of what an agent needs to call it 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 all ten parameters are already documented. The description restates the filter families (season, team, position, BIP/PA qualifier and threshold) and mentions local sorting and pagination, matching but not extending the schema. 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+resource ('Get Baseball Savant Expected Statistics') and describes the leaderboard nature with its views and filters. It distinguishes itself from mlb_statcast and mlb_statcast_oaa by naming Expected Statistics specifically, though it does not explicitly call out the sibling boundary.

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?

Usage is implied by the described filters and leaderboard views, so an agent can infer this is for expected-stat leaderboards rather than general Statcast or OAA data. However, there is no explicit when-to-use/when-not guidance or reference to the sibling tools for those other cases.

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