Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_pitch_arsenal

Fetch MLB pitcher or batter pitch-arsenal leaderboards from Baseball Savant, with filters for season, team, pitch type, minimum PA or pitches, plus sorting and pagination.

Instructions

Get Baseball Savant Pitch Arsenal Stats. Returns pitcher or batter pitch-level arsenal leaderboards. Season, team, pitch type, minimum PA, and minimum-pitch qualification filters are replayed against the anonymous first-party table; sorting and pagination are applied locally. Use mlb_discovery for the full selector set. Player rows can be expanded with mlb-statcast-pitch-arsenal-details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoLocal sort field
typeNoRow type
yearNoSeason
limitNoRows per page (1-500)
min_paNoMinimum plate appearances
offsetNoZero-based row offset
team_idNoMLB team id from mlb_teams
sort_dirNoLocal sort direction
pitch_typeNoPitch code; blank means all pitch types
min_pitchesNoMinimum pitches; q means qualified

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 burden. It usefully discloses the processing model ('filters are replayed against the anonymous first-party table; sorting and pagination are applied locally'), which tells the agent results are locally sorted/paginated. It does not state auth needs, rate limits, or read-only nature explicitly.

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 the purpose, then filters/processing, then sibling routing. Little waste, though the dense 'anonymous first-party table' clause is slightly jargon-heavy.

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 10-parameter, no-required-arg tool with no output schema, the description covers purpose, filter semantics, local sorting/pagination behavior, and related-tool routing. Reasonably complete, though it lacks any detail on returned row fields that would help given the absent output schema.

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%, so the schema already documents all ten parameters and their enums. The description restates the filter categories (season, team, pitch type, min PA, min-pitch qualification) without adding syntax or meaning beyond the schema. 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+resource ('Get Baseball Savant Pitch Arsenal Stats') and clarifies it returns 'pitcher or batter pitch-level arsenal leaderboards', which is a meaningful scope distinction. It names the related details tool for expansion, though it does not differentiate from the confusingly similar sibling 'mlb_statcast_pitch_arsenals'. Clear purpose overall but sibling disambiguation is only partial.

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 context ('Use mlb_discovery for the full selector set') and notes that rows can be expanded via mlb-statcast-pitch-arsenal-details. However, it gives no when-to-use vs the near-identical plural sibling nor any exclusions, leaving gap. Implied usage rather than explicit guidance.

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