Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_pitch_timer

Retrieve Baseball Savant Pitch Timer infraction rows for pitchers, batters, catchers, teams, or opponents. Filter by season, type, and minimum pitches; sort or paginate results locally.

Instructions

Get Baseball Savant Pitch Timer infraction rows. Returns the Pitch Timer Infractions table for pitchers, batters, catchers, teams, or opposing teams. Filters for type, season, minimum pitches, and zero-infraction rows are upstream-backed; entity search, table sorting, and pagination are applied locally. The chart ordering is included as view metadata; the endpoint returns table rows, not the SVG chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoLocal case-insensitive entity-name substring filter
sortNoLocal table sort field
typeNoEntity group
limitNoRows per page (1-500)
offsetNoZero-based row offset
seasonNoSeason
sort_dirNoSort direction
chart_sortNoChart ordering metadata
min_pitchesNoMinimum pitches
include_zeroesNoInclude entities without infractions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses which filters are applied upstream vs locally, and clarifies that chart ordering is metadata while the endpoint returns table rows—useful processing context. However, it doesn't state whether this is a read-only operation, what the return format looks like, or any rate limits/auth needs.

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 with a logical flow: purpose, scope, then technical behavior about processing locations and output. It's front-loaded with the core purpose and avoids unnecessary repetition, though the sentence about chart ordering and table rows could be seen as slightly tangential for an agent focused on data retrieval.

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?

Given 10 optional parameters, no output schema, and no annotations, the description does a good job clarifying the processing model (which filters are upstream vs local) and the fact that it returns table rows rather than a chart. The main gap is that it doesn't describe the shape of the returned rows, which would be helpful without an output 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 coverage is 100%, so the schema already explains each parameter thoroughly. The description adds little beyond noting that some filters are upstream-backed and others local, which is marginally helpful but not parameter-specific. Baseline 3 is appropriate given the schema does the heavy lifting.

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 Pitch Timer infraction rows'), and clarifies it returns the Pitch Timer Infractions table for pitchers, batters, catchers, teams, or opposing teams. It distinguishes itself from the sibling mlb_statcast_pitch_tempo by naming 'Pitch Timer' rather than tempo, but doesn't explicitly contrast with 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?

Usage is implied by the description of what the tool returns, but there are no explicit when-to-use or when-not-to-use statements, nor are any alternatives (like mlb_statcast_pitch_tempo) mentioned. The description says what it does but not when to choose it over another tool.

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