Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_catcher_framing

Fetch MLB Baseball Savant catcher framing leaderboard rows by catcher, team, batter, pitcher, league, season, date, pitch type, or call model, with filters, sorting, and pagination.

Instructions

Get Baseball Savant Catcher Framing leaderboard rows. Returns the Catcher Framing table for catcher, catching-team, batter, batting-team, pitcher, or league groups. Supports observed game, season, one-team, pitch/result minimum, date, bat-side, pitch-hand, pitch-type, ball/strike, and call-model filters, plus local sort and pagination. Use mlb_discovery for exact enum values; chart-only groupings and player comparison controls are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callNoFraming model
sortNoLocal sort field
teamNoOptional single MLB team id
typeNoTable group
limitNoRows per page (1-500)
offsetNoZero-based row offset
bat_sideNoBatter side
date_endNoInclusive end date
sort_dirNoLocal sort direction
game_typeNoGame type
date_startNoInclusive start date
pitch_handNoPitcher hand
pitch_typeNoSingle pitch type
season_endNoLast season
ball_strikeNoPitch location relative to strike zone
min_pitchesNoMinimum pitches
min_resultsNoMinimum results
season_startNoFirst season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose read-only leaderboard retrieval, local sort, pagination, and excluded features, but it omits authorization/rate-limit context, default season behavior, and any detail about what the returned table contains.

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?

Purpose is front-loaded in the first sentence, and each subsequent sentence adds distinct value: group coverage, supported filter families, and exclusions/enum guidance. It is dense but not bloated for an 18-parameter tool.

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?

The description covers the tool’s purpose, major filter families, sort/pagination behavior, and important exclusions, making it usable for a complex 18-parameter tool. It is incomplete only in that, with no output schema, return columns and default date/season behavior remain implicit.

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 groups the parameter families (season, team, date, pitch/result minimum, bat-side, pitch-hand, pitch-type, ball/strike, call model), but adds no format, default, or inter-parameter semantics beyond what the schema already documents.

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 and resource: 'Get Baseball Savant Catcher Framing leaderboard rows.' It also lists the supported group types, which sharpens scope. However, it does not distinguish this tool from sibling mlb_statcast_catcher_framing_details, so it stops short of a 5.

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?

Gives useful routing guidance by telling the agent to use mlb_discovery for exact enum values and by noting that chart-only groupings and player comparison controls are excluded. It still does not explain when to choose this leaderboard tool over related sibling tools such as mlb_statcast_catcher_framing_details.

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