Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_rolling

Fetch Baseball Savant rolling-window rows for batters and pitchers, filtered by metric, role, and plate-appearance window, with per-group sorting and pagination.

Instructions

Get Baseball Savant Rolling Windows rows. Returns the six embedded Batter/Pitcher rolling-window tables, filtered by metric, role, and plate-appearance window. Each group is sorted by the selected metric delta in the same direction as the first-party page and paginated independently. The upstream page has no season, team, or game-type filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoOptional player role; omit for both
limitNoRows per group (1-500)
metricNoDisplayed metric
offsetNoZero-based row offset per group (0-5000)
window_paNoOptional rolling plate-appearance window; omit for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 full behavioral burden. It discloses useful context on sorting ('sorted by the selected metric delta in the same direction as the first-party page') and independent pagination per group, which the annotations do not supply. However, it doesn't state whether calls are read-only, whether the data is a snapshot or live, or any rate/return-shape details beyond 'rows'.

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 sentences are dense and front-loaded with the response shape. Slightly more than needed, but each sentence carries distinct information (what is returned, how it is grouped/sorted/paginated, what is unsupported).

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?

It explains the response structure and the sorting logic, which is important for an unpaginated-by-default ranking tool. However, with no annotations and no output schema, the description does not state whether the operation is safe/read-only or how the 'six embedded tables' relate to the role/window filters when omitted, leaving an agent to infer behavior from the 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 fully documents all five parameters including enums and ranges. The description adds no syntax or default details beyond the header language. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Specific verb (Get) and resource (Baseball Savant Rolling Windows rows), and it quantifies the response shape as six embedded Batter/Pitcher tables. An agent can distinguish this rolling-window leaderboard tool from the numerous other mlb_statcast_* siblings.

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?

There is an explicit negative constraint: 'The upstream page has no season, team, or game-type filters,' which tells the agent not to supply those. But it never names an alternative tool or states when to prefer this rolling-window view over the static mlb_statcast or mlb_statcast_expected siblings. Usage is implied rather than routed.

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