Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_pitch_tempo

Retrieve Baseball Savant pitch tempo data by pitcher, batter, team, or league. Filter by season, game type, and minimum pitches, then sort and paginate results.

Instructions

Get Baseball Savant Pitch Tempo rows. Returns pitcher, batter, pitching-team, batting-team, or league tempo rows. Season, game type, minimum pitch, team, year comparison, and team membership options mirror the live first-party controls; q and sorting are applied locally before pagination. Use mlb_discovery for exact value sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoMinimum pitch count
qNoCase-insensitive local entity-name filter
sortNoLocal sort field
teamNoOptional MLB team id
typeNoTable group
limitNoRows per page (1-500)
splitNoCompare seasons separately
offsetNoZero-based row offset
sort_dirNoSort direction
game_typeNoGame type
season_endNoLast season; must be >= season_start
season_startNoFirst season
with_team_onlyNoTeam membership mode; requires team

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 behavioral burden. It usefully discloses that q and sorting are applied locally before pagination, which is real behavioral information beyond the schema, but it says nothing about rate limits, response shape, or pagination bounds.

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?

Three compact sentences with the purpose front-loaded and the parameter-mapping and local-filtering notes following. No filler, though the second sentence is somewhat parameter-enumerative.

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 13-parameter, zero-required, no-output-schema tool, the description covers purpose, the primary row-type dimension, local filtering/pagination behavior, and points to mlb_discovery. The rich enum schema fills in the remaining detail, so an agent has enough 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% and 10 of 13 params carry enums, so the schema already documents each parameter. The description adds only marginal meaning (row-type groups, season comparison) and essentially restates the first-party control mapping. 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 and resource ('Get Baseball Savant Pitch Tempo rows') and enumerates what the rows represent (pitcher, batter, pitching-team, batting-team, league tempo), which hints at the `type` dimension. It does not explicitly distinguish itself from the near-name siblings mlb_statcast_pitch_tempo_player or mlb_statcast_pitch_timer, so it is clear but not fully self-differentiating.

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?

It routes the agent to mlb_discovery for exact value sets, which is genuinely useful, and implies the row-type/season/team options mirror first-party controls. However, it never states when to choose this tool over pitch_tempo_player or pitch_timer, so usage is only implied.

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