Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_pitch_tempo_player

Retrieve game-level Pitch Tempo detail rows for a pitcher or batter by entity ID, including elapsed seconds, counts, and frequencies across chosen seasons and game types.

Instructions

Get a player's Pitch Tempo detail rows. Returns game-level Pitch Tempo detail rows for one pitcher or batter. entity_id is required, taken from a Pitch Tempo result. type is Pit (default) or Bat, season_start and season_end run from 2010 to 2026 and default to the current year, and game_type is Regular (default), Playoff or All. Rows hold elapsed seconds, counts and frequencies; empty when nothing matches.

Input Schema

NameRequiredDescriptionDefault
typeNoEntity type
entity_idYesNumeric entity id from a Pitch Tempo row
game_typeNoGame type
season_endNoLast season; must be >= season_start
season_startNoFirst season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses default values (Pit, Regular, current year), the season range (2010-2026), the required key, and the empty-result behavior ('empty when nothing matches'). It does not cover auth, rate limits, or pagination, but for a read-only stat query it discloses the behaviors an agent most needs.

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?

Roughly four dense sentences, front-loaded with purpose and return scope before parameter details and the empty-result caveat. No filler; each sentence conveys a distinct fact (purpose, source of entity_id, param defaults/ranges, row contents).

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 5-parameter read tool with no output schema and no annotations, the description covers purpose, prerequisite, defaults, enum values, season bounds, returned row contents, and empty behavior. It is essentially self-sufficient; only absent details like pagination or rate limits keep it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds value beyond the schema by surfacing defaults the schema omits (type=Pit, game_type=Regular, seasons=current year) and restating the enum vocabularies and season bounds in one place. The only gap is that it repeats rather than expands on the schema's per-parameter descriptions.

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 a player's Pitch Tempo detail rows' / 'game-level Pitch Tempo detail rows for one pitcher or batter'), and the scope (single entity, pitcher or batter) is clear. It implicitly routes the agent by noting entity_id is 'taken from a Pitch Tempo result', but it never names the sibling tool (mlb_statcast_pitch_tempo) explicitly as the feeder, so the differentiation is suggested rather than stated.

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?

Provides the key prerequisite chain: entity_id must come from a prior Pitch Tempo result, so the agent knows this is a detail-drilldown after a list call. It does not, however, state when not to use it or name an alternative filter tool explicitly, so the guidance stops short of full routing.

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