Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_top_performers

Retrieve Baseball Savant Top Performers cards for a selected MLB season, showing batter and pitcher rankings across batting, expected-stat, fielding, running, and pitch metrics.

Instructions

Get Baseball Savant Top Performers. Returns every current Top Performers card for the selected season, including batter and pitcher rankings across batting, batted-ball, expected-stat, fielding, catching, running, and pitch-metric views. The page exposes a season selector but no per-card filters; use the specialist Statcast endpoints for complete filtered leaderboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoSeason from 2015 through the current season; defaults to the current season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully discloses that the tool returns every current Top Performers card and has no per-card filters. That is meaningful behavioral context, though it does not cover response format, pagination, or permission requirements.

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: the resource and return scope come first, followed by the usage caveat and the alternative endpoint. Every sentence earns its place and nothing is unnecessarily repeated.

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 one-parameter read tool with no output schema, the description gives enough detail to select and call it correctly, including return scope and filtering limitations. It could be slightly stronger by noting that the result is a bulk unfiltered set, but the schema and description together are sufficient.

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?

The schema description already covers the only parameter at 100%, including its 2015-current range and default to the current season. The description adds only the concept of a 'selected season' and does not extend parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource ('Baseball Savant Top Performers') and states exactly what it returns: every current card for the selected season across several ranking categories. It also distinguishes this tool from the specialist Statcast endpoints, so an agent can tell it apart from siblings without opening the schema.

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

Usage Guidelines5/5

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

It explains the usage boundary explicitly: the page exposes only a season selector and no per-card filters, and it directs agents to specialist Statcast endpoints for complete filtered leaderboards. This gives both when to use this tool and when to use an alternative.

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