Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_sprint_speed_teams

Fetch MLB Statcast Sprint Speed team rows and sort or filter by team, season, sprint speed, or bolts for club baserunning comparisons.

Instructions

Get Baseball Savant Sprint Speed team rows. Returns team-level Sprint Speed rows. Season is selected upstream; team filtering and sorting are applied locally because the first-party page embeds every team before its client-side filter. Use mlb_discovery for all accepted seasons, teams, and sort fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoLocal sort field
teamNoOptional first-party team selector abbreviation
limitNoRows per page (1-500)
offsetNoZero-based row offset
seasonNoSeason or all seasons
sort_dirNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose non-obvious traits: season is selected upstream, and team filtering/sorting are applied locally because the first-party page embeds every team before its client-side filter. It does not mention auth, rate limits, or return shape, but the local-filtering disclosure is genuinely useful.

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?

Front-loaded and short, but the first two sentences are near-duplicates ('Get ... Sprint Speed team rows' / 'Returns team-level Sprint Speed rows'), which is mild redundancy rather than added 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 a no-annotation, no-output-schema list tool, the description covers the important operational facts (upstream season selection, local filtering/sorting) and points at the discovery tool for enums. Nothing critical to calling it correctly is missing, though return-shape expectations remain implicit.

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 meaning by clarifying that the season is selected upstream and that team/sort fields are resolved via mlb_discovery, which explains why the params behave the way they do. It stops short of describing pagination semantics for limit/offset.

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 states a specific verb (Get) and resource (Baseball Savant Sprint Speed team rows) and immediately scopes it to team-level output, which cleanly separates it from the player-level mlb_statcast_sprint_speed sibling. An agent can tell what it retrieves 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 Guidelines4/5

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

It gives a clear routing rule: use mlb_discovery for all accepted seasons, teams, and sort fields, and it explains that filtering/sorting happen locally. It lacks an explicit when-not-to-use statement for the player-level counterpart, but the context is clear.

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