Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_catcher_stance

Fetch Baseball Savant catcher stance rows for catchers, teams, batters, pitchers, or league totals; filter by season, date, pitch type, and knee posture.

Instructions

Get Baseball Savant Catcher Stance rows. Returns the public Catcher Stance table for catchers, catching teams, batters, batting teams, pitchers, or league totals. Supports the live year, game, date, threshold, team, pitch type, batter/pitcher hand, knee posture, grouping, sorting, and pagination controls. Grouping accepts up to four values. Use mlb_discovery for exact value sets. Chart series and page-local search/column toggles are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoLocal row sort field
typeNoTable entity type
limitNoRows per page (1-500)
teamsNoOne or more MLB team ids
offsetNoZero-based row offset
bat_sideNoBatter side; omit for all
date_endNoEnd date YYYY-MM-DD
group_byNoUp to four grouping dimensions; none disables grouping
sort_dirNoSort direction
game_typeNoGame type
knee_codeNoKnee posture
date_startNoStart date YYYY-MM-DD
pitch_handNoPitcher hand; omit for all
season_endNoLast season; must be >= season_start
min_pitchesNoMinimum pitches
min_resultsNoMinimum results
pitch_typesNoOne or more pitch types
season_startNoFirst season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries full burden. It discloses scope constraints (grouping accepts up to four values) and negative scope (chart series and page-local search/column toggles are not included), which is valuable. But it omits auth needs, default limit/offset behavior, and pagination semantics for a read tool with 18 params.

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?

Front-loaded with the purpose, then the entity scope, then supported controls, and closes with the exclusions and the discovery pointer. Five sentences, no filler, all serving a purpose, though the control enumeration is a dense run-on that could be tightened.

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-param tool with no annotations and no output schema, the description covers entity scope, the control surface, grouping limits, exclusions, and where to find valid values. It stops short of describing return shape, defaults, or pagination behavior, which the absent output schema would otherwise require it to carry.

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 11 enums, so the schema already documents each parameter well. The description adds a categorical summary of the control groups (year, date, threshold, team, pitch type, hand, knee posture, grouping, sorting, pagination) but no syntax, format, or default details beyond the schema. Baseline 3 is appropriate.

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') plus the exact resource ('Baseball Savant Catcher Stance rows') and enumerates the entity types the table covers (catchers, teams, batters, pitchers, league). This is clearly distinct from generic MLB tools, though it never names the sibling catcher tables (framing, blocking, throwing, pop_time) that an agent might confuse it with.

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?

Provides one explicit routing hint ('Use mlb_discovery for exact value sets'), which is genuinely useful for the many enum parameters. However, it gives no guidance on when to prefer this catcher-stance table over the ~15 sibling mlb_statcast_catcher_* tools, leaving the core selection decision to inference.

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