Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_pitch_movement

Fetch pitcher-level pitch movement rows from Baseball Savant by season, pitch type, throwing hand, and minimum pitch count, with local sorting and pagination.

Instructions

Get Baseball Savant Pitch Movement rows. Returns pitcher-level pitch movement table rows for the selected season, pitch type, throwing hand, and minimum pitch count. Sorting and pagination are applied locally. The page's X/Z visualization axes and CSV download are separate presentation formats and are not returned by this JSON table contract.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minNoMinimum pitch count
handNoPitcher throwing hand; omit for both
sortNoLocal table sort field
yearNoSeason
limitNoRows per page (1-500)
offsetNoZero-based row offset
sort_dirNoSort direction
pitch_typeNoPitch class

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.3/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/pagination are applied locally and that X/Z visualization axes and CSV download are NOT returned — a real contract detail. But it says nothing about auth, rate limits, or the fact that all 8 filters are optional (so defaults matter).

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?

Three tight sentences, front-loaded with the purpose, and the final sentence earns its place by ruling out commonly-assumed outputs (axes/CSV). No filler.

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?

With no output schema and no annotations, the description reasonably frames the JSON-table contract and exclusions, but omits the shape/columns of returned rows and doesn't clarify defaults when zero required params are supplied. Adequate but with clear gaps for an 8-param analytical tool.

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 enums on 6 of 8 params, so the schema already fully documents each parameter. The description only restates the filter set (season, pitch type, hand, min count) without adding format or default semantics beyond the schema — baseline 3.

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 Movement rows") and clarifies the granularity ("pitcher-level pitch movement table rows"). It's clear what the tool returns, but it never distinguishes itself from the many sibling mlb_statcast_* tools (e.g. pitch_arsenal, active_spin), which an agent must do on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the filters it honors (season, pitch type, hand, min count) but gives no explicit when-to-use / when-not-to-use guidance and names no alternative. For a large family of near-identical statcast table tools, the agent gets no routing help.

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