Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_catcher_throwing

Fetch Baseball Savant catcher throwing leaderboard rows by season, team, game, target base, and steal attempts to analyze caught-stealing and throw-quality stats.

Instructions

Get Baseball Savant Catcher Throwing leaderboard rows. Returns catcher, catching-team, or league caught-stealing and throw-quality rows with the public season, game, attempt-threshold, target-base, split-years, team, and roster-membership filters. Table sorting and pagination are applied locally. Catcher rows can be expanded with mlb-statcast-catcher-throwing-details. CSV, charts, and page-local display controls are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoLocal sort field
teamNoEmpty for all teams, split for team stints, or an MLB team id
typeNoTable group
limitNoRows per page (1-500)
splitNoSplit results by season
offsetNoZero-based row offset
minimumNoMinimum steal attempts
sort_dirNoLocal sort direction
game_typeNoGame type
season_endNoLast season; must be >= season_start
target_baseNoThrow target
season_startNoFirst season
with_team_onlyNoFor a selected team, include only catchers on that team

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 are provided, so the description carries the full burden. It usefully discloses that sorting and pagination are applied locally and that CSV, charts, and page-local display controls are excluded, which is genuine behavioral context. However, it omits data source refresh cadence, whether output is cached, and the shape of the returned rows beyond field names.

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?

Four compact sentences, front-loaded with purpose then scope then expansion path then exclusions. No filler. Slightly dense for the amount of information but well organized.

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 a 13-parameter, no-required, no-output-schema, no-annotation tool, the description covers purpose, filters, local sort/pagination, and expansion path. What is missing is return-shape detail (why an agent should care) and whether empty required params yield an unfiltered default or an error, which matters given zero required parameters.

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% and every parameter has an inline description, so the schema does the heavy lifting. The prose enumerates filter categories (season, game, attempt-threshold, target-base, split-years, team, roster-membership) without adding syntax, defaults, or ranges 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 the specific verb+resource: baseball Savant catcher throwing leaderboard rows, with the row types (catcher, catching-team, league) made explicit. Sibling mlb_statcast_catcher_throwing_details is named, so the boundary is clear. Missing only a concise differentiator from sibling catcher tools like catcher_pop_time or catcher_framing.

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?

Points to the details sibling for expansion, which implies when to use this one instead, but there is no explicit when-to-use or when-not-to-use guidance versus the many other mlb_statcast_catcher_* tools. The usage context is implied rather than stated.

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