Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_birthday_index

Retrieve Baseball Savant birthday index rows for MLB batters and pitchers, including today's and upcoming birthday stats, with filters for date, type, and minimum games.

Instructions

Get Baseball Savant Sarah Langs Birthday Index rows. Returns today's birthday tables for batters and pitchers plus the selected upcoming-birthday table. Type and minimum-games are first-party filters; date must fall inside the live page's season date range. The active-player toggle, sorting, and pagination are applied locally. The MLB Terms of Use notes a private, non-commercial-use boundary and restrictions on redistribution; this endpoint exposes statistical rows only and excludes media, graphics, and CSV.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoOptional birthday date in M-D form; accepted dates are bounded by the current live page season window
sortNoLocal sort column. Some values are type- or date-specific and invalid combinations are rejected.
typeNoUpcoming table
limitNoRows per page (1-500)
offsetNoZero-based row offset (0-5000)
sort_dirNoLocal sort direction; omitted values use the selected column's live first-party initial direction
min_gamesNoMinimum games played on the birthday
show_inactivesNoInclude inactive and deceased players in upcoming rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations to lean on, the description carries the full burden well: it discloses that some filters are first-party (server) while toggle, sorting and pagination are applied locally, that the date is season-bounded, that only statistical rows are returned (excluding media/graphics/CSV), and flags MLB Terms of Use non-commercial/redistribution restrictions. Return-shape and error behavior are the only notable gaps.

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?

The first sentence front-loads the resource and the return description follows logically. It is dense but mostly every sentence earns its place; the trailing legal sentence is the only part that could be trimmed without losing invocation-relevant meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-annotation, no-output-schema tool, the description covers what it returns (two fixed tables plus the selected upcoming table), which parameters are server- versus client-side, the date constraint, and the usage/licensing boundary. An agent has enough to call it correctly without opening anything else.

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, and the description adds genuine semantics beyond the schema by classifying parameters as first-party filters (type, min_games) versus locally applied ones (active-player toggle, sort, pagination). It does not add format detail for date or limit/offset, but it meaningfully clarifies parameter behavior.

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?

The description names a specific verb and a highly specific resource ('Get Baseball Savant Sarah Langs Birthday Index rows') and immediately states what is returned (today's batter/pitcher tables plus the selected upcoming table). It is clearly distinguishable from generic baseball tools, though it never explicitly contrasts itself with the many sibling mlb_statcast_* endpoints.

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?

It gives operative constraints — date must fall inside the live page's season window, and type/min_games are first-party filters — which implies correct usage. However, it never states when to choose this tool over alternatives or what prerequisites/preconditions the caller must satisfy before invoking it.

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