Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_catcher_blocking

Retrieve Baseball Savant catcher blocking leaderboard rows filtered by season, team, game type, minimum opportunities, and sort order for catcher, pitcher, team, or league analysis.

Instructions

Get Baseball Savant Catcher Blocking leaderboard rows. Returns catcher, pitcher, catching-team, or league Catcher Blocking rows. Filters cover game type, season range, minimum opportunities, team/stint, and local table sorting. Use mlb_discovery for the exact filter sets. Row detail events are available from mlb-statcast-catcher-blocking-details; chart playback and CSV export controls are not data rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minNoMinimum opportunities; applies to Cat and Pit
sortNoLocal sort field from mlb_discovery
teamNoOptional team filter: split or an MLB team id from mlb_discovery
typeNoLeaderboard group
limitNoRows per page (1-500)
splitNoSplit rows by season
offsetNoZero-based row offset
end_yearNoLast season, start_year through current season
sort_dirNoLocal sort direction
game_typeNoGame type
start_yearNoFirst season, 2018 through current season
with_team_onlyNoFor a specific Cat or Pit team, include only rows for that team; defaults true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses the row groupings and the fact that chart/CSV controls are non-data, but says nothing about pagination interaction (limit/offset), auth or rate limits, or the default sorting behavior.

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 tight sentences, front-loaded with the resource and return shape, then filters, then routing, then exclusions. No filler, though the filter enumeration slightly restates the schema.

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?

Covers return shape, filter scope, sibling routing and non-data exclusions for a 12-param read tool with no output schema. Complete enough for correct invocation, though pagination and default-sort behavior are left entirely to the schema.

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 schema already documents all 12 parameters including enums. The description adds marginal value by grouping the filters (game type, season range, min opportunities, team/stint, sorting) but no syntax or semantics beyond the schema.

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?

States a specific verb (Get) and resource (Baseball Savant Catcher Blocking leaderboard rows), and enumerates the row entity types returned (catcher, pitcher, catching-team, league). This distinguishes it clearly from the detail/event sibling without needing to open either schema.

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?

Explicitly routes the agent to mlb_discovery for exact filter sets and names the sibling tool that provides row detail events, plus declares what is NOT a data row (chart playback, CSV export). It gives clear context but no explicit when-not-to-use beyond those pointers.

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