Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_abs_challenges

Retrieve Baseball Savant ABS challenge rankings and filtered tables by season, team, pitch type, leverage, and breakeven to analyze challenge outcomes.

Instructions

Get Baseball Savant ABS challenge rankings. Returns Baseball Savant's ABS challenge table with repeated season, game type, split, challenging-team, opponent-team, pitch-type, and shadow-zone filters, plus challenger type, level, thresholds, leverage, pitch location, breakeven, and split-year controls. Filter values are live-verified and listed by /mlb/discovery. The entire filtered table is returned; UI-only drawer details and client-side sorting are not separate source filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoCompetition level
splitsNoSplit dimensions
seasonsNoSeason values
leverageNoLeverage bucket; empty selects All
breakevenNoChallenge breakeven band; empty selects All
data_modeNoChallenges made or against
data_countNoChallenge count or run value
game_typesNoGame type codes
split_yearNoSeparate year groups
ball_strikeNoPitch location; empty selects All
pitch_typesNoPitch type codes
shadow_zonesNoShadow zone codes
challenge_typeNoChallenge board group
min_challengesNoMinimum challenges made
opponent_team_idsNoOpponent MLB team ids
challenge_team_idsNoChallenging MLB team ids
min_opponent_challengesNoMinimum challenges against

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/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 does add real behavioral context: it states the entire filtered table is returned, that filter values are live-verified via /mlb/discovery, and that client-side sorting and drawer details are not server-side filters. It does not cover permissions, rate limits, or return shape, but for a read-only ranking table it discloses meaningful scope beyond the schema.

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, front-loaded with what the tool returns, then filter sourcing, then scope caveats. It is dense but each sentence earns its place by adding filter provenance or output-scope information rather than restating the name.

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 17-parameter, no-required, read-only table tool with 100% schema coverage and no output schema, the definition covers what is fetched, how filters are sourced, and what is not separately filterable. It stops short of describing the ranking columns, but the schema and lack of output schema make this largely 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?

Schema description coverage is 100% with per-property descriptions and enums, so the schema already documents every one of the 17 parameters. The description enumerates filter categories at a high level but adds no format, default, or interaction details beyond what the schema provides, so the baseline of 3 applies.

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 ABS challenge rankings,' and echoes the concrete table name. It is clearly about ABS challenge rankings, which is distinguishable by name from other mlb_statcast_* siblings, but the description never explicitly contrasts itself with those related pitching/statcast tools.

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 helpfully routes the agent to /mlb/discovery to enumerate filter values and notes that UI-only drawer details are not separate source filters, so there is implied usage guidance. However, it never states when to prefer this tool over sibling statcast tools or any preconditions/exclusions in explicit terms.

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