Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_home_runs_details

Retrieve expanded home-run play details from Baseball Savant for a chosen MLB batter or pitcher, including event measurements, park outcomes, and source links.

Instructions

Get Baseball Savant Home Runs play details. Returns the home-run plays expanded from one batter or pitcher leaderboard row, with event measurements and park outcomes. Provide the exact player id, player type, year, and mode from the row. Play identifiers and source links are returned; trajectory images, video media, and CSV output are not included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catNoTrajectory mode
yearNoSeason
limitNoRows per page (1-500)
offsetNoZero-based row offset
player_idYesPositive MLB player id from mlb-statcast-home-runs
player_typeNoTable type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/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 a good job: it names what is returned (play identifiers, source links, event measurements, park outcomes) and explicitly excludes trajectory images, video media, and CSV output. It does not address pagination despite the limit/offset parameters, leaving a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: purpose, return/scope, then input sourcing. The what-it-does statement is front-loaded and nothing is redundant.

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 6-parameter read tool with no output schema and no annotations, the description covers purpose, sourcing of inputs, and the shape/limits of the return value. Pagination semantics for limit/offset are the only notable omission.

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 real meaning by tying player_id/player_type/year/mode to the originating leaderboard row and framing them as the row's values. It does not clarify limit/offset behavior, so it doesn't reach the top.

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?

States a specific verb and resource ('Get Baseball Savant Home Runs play details') and clarifies the scope: it expands the home-run plays behind a single batter/pitcher leaderboard row. This cleanly distinguishes it from the sibling mlb_statcast_home_runs, which produces those leaderboard rows.

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?

The description instructs the agent to 'Provide the exact player id, player type, year, and mode from the row,' making clear this is a drill-down that requires values obtained from a prior leaderboard query. It stops short of naming the sibling tool or stating when not to use this 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