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 time buckets for a selected MLB pitcher or batter using their entity ID from a pitch tempo result.

Instructions

Get a player's Pitch Tempo detail rows. Returns game-level time buckets for the selected pitcher or batter. Use entity_id from an mlb_statcast_pitch_tempo result.

Input Schema

TableJSON 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

A3.6/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 discloses the return shape ('game-level time buckets'), which helps, but says nothing about permissions, rate limits, pagination, or whether results are paginated/deprecated. Adequate but thin for a tool with zero annotation coverage.

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 short sentences, front-loaded with purpose then return shape then prerequisite; no filler. Slightly compressed relative to what it could explain, but nothing is wasted.

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 simple read-only lookup with a fully-described schema and no output schema, the description covers purpose, scope, and input provenance. The main residual gap is return-format specifics, which the missing output schema could have covered.

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% with 4 of 5 parameters enum-constrained, so the schema already documents everything. The description reinforces the entity_id provenance and implies the Pit/Bat distinction via 'pitcher or batter', but adds no syntax or defaulting detail beyond the schema. Baseline 3 applies.

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', and the second sentence specifies the scope as game-level time buckets for a pitcher or batter. This distinguishes it from the sibling mlb_statcast_pitch_tempo by framing it as the per-entity detail view, though it never explicitly names the parent as the alternative.

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?

'Use entity_id from an mlb_statcast_pitch_tempo result' gives an explicit prerequisite and call-ordering chain, which is exactly the guidance an agent needs for a follow-up tool. It stops short of stating when-not-to-use it or naming alternatives beyond the implicit parent call.

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