Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_pitch_arsenals

Retrieve Statcast pitch arsenal rankings for MLB pitchers by speed, usage, or spin. Filter by season, minimum pitches, hand, and team to compare repertoires.

Instructions

Get Baseball Savant Pitch Arsenals. Returns pitcher pitch speed, percentage, or spin rankings by pitch class. Year, minimum-pitch threshold, and hand are first-party filters. Team filtering and table sorting are applied locally because the page JavaScript applies them after receiving the embedded rows. Use mlb_discovery for exact values. CSV and pitch movement visualizations remain separate representations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handNoThrowing hand; omit for all pitchers
sortNoLocal sort column
teamNoCurrent MLB team abbreviation; applied locally
typeNoMetric
yearNoSeason
limitNoRows per page (1-500)
offsetNoZero-based row offset
sort_dirNoLocal sort direction
min_pitchesNoMinimum pitches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden, and it usefully discloses non-obvious behavior: which filters are first-party (year, min-pitches, hand) versus applied locally (team filtering and sorting handled after the embedded rows are fetched). It does not cover auth, rate limits, or pagination defaults, so it is strong but incomplete for a zero-annotation tool.

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?

Front-loads purpose and return content in the first two sentences, then adds filtering-behavior context; the local/first-party split is compact. The closing sentence ('CSV and pitch movement visualizations remain separate representations') is somewhat vague and jargon-adjacent but still earns its place as a routing note.

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 9-parameter, zero-required, no-output-schema, no-annotation tool, the description covers what is returned, the filter semantics, and the unusual local-vs-first-party behavior. Pagination defaults (limit/offset) and the exact row shape are not explained, but the core need for calling the tool is addressed.

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 the schema already labels team/sort as 'applied locally' and 'Local sort column', so the description largely echoes structured data. It does map the metric options to speed/percentage/spin, adding marginal gloss over the type enum, but this is the baseline case where the schema does the heavy lifting.

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 Arsenals') and clarifies the payload: pitcher pitch speed, percentage, or spin rankings by pitch class. It differentiates from pitch-movement ('pitch movement visualizations remain separate') but does not distinguish itself from the near-identically named siblings mlb_statcast_pitch_arsenal and mlb_statcast_pitch_arsenal_details.

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?

Provides routing hints such as 'Use mlb_discovery for exact values' and notes that CSV/pitch-movement outputs are separate, which implies when this tool fits. However, there is no explicit when-to-use vs the closely-named pitch_arsenal sibling and no stated exclusions, 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