Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_percentile

Retrieve Baseball Savant percentile rankings for MLB batters or pitchers by season and team, with local percentile filters, sorting, and pagination.

Instructions

Get Baseball Savant Percentile Rankings. Returns batter or pitcher percentile rankings. Type, season, and team are first-party table filters. Repeated pctl filters, table sorting, and pagination are applied locally to the embedded rows. Use mlb_discovery for exact type-specific fields, comparators, seasons, and team ids. CSV is a separate download.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pctlNoRepeated field-comparator-value filter from the type-specific field set in mlb_discovery; value range 0-100
sortNoLocal sort field from the type-specific set in mlb_discovery
teamNoMLB team id; blank selects all teams
typeNoTable type
yearNoSeason
limitNoRows per page (1-500)
offsetNoZero-based row offset
sort_dirNoLocal sort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/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 delivers valuable behavioral detail: it distinguishes first-party table filters (type, season, team) from locally-applied pctl filters, sorting, and pagination over embedded rows, and notes CSV is a separate download. It omits auth/rate-limit info, but the filtering-execution model is a meaningful disclosure.

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?

Five tight sentences, front-loaded with purpose before mechanics and the mlb_discovery pointer. Nearly every sentence earns its place; the 'CSV is a separate download' note is slightly peripheral but still useful scope information.

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 an 8-parameter tool with no annotations and no output schema, the description covers purpose, filter semantics, and routing to a companion tool. It does not describe pagination defaults, return fields, or limits, but overall it is complete enough for an agent to call correctly.

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 the baseline is 3, but the description adds semantics the schema cannot convey: which parameters are server-side table filters (type, season, team) versus locally-applied operations (pctl, sort, pagination). This clarifies the execution model of the parameters beyond their type/enum definitions.

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 Percentile Rankings') and clarifies the return shape ('batter or pitcher percentile rankings'). It is distinct from sibling statcast tools by focusing on percentile rankings, though it does not explicitly contrast itself with mlb_statcast or the other statcast variants.

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 a useful routing hint ('Use mlb_discovery for exact type-specific fields, comparators, seasons, and team ids') and notes CSV is a separate download, but never states when to choose this tool over the many other mlb_statcast_* siblings. Usage context is implied rather than explicit.

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