Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

mlb_statcast_arm_strength

Fetch MLB player/team arm strength leaderboards or individual throw records from Baseball Savant with season, team, position, min-throws, sorting, and pagination filters.

Instructions

Get Baseball Savant Arm Strength leaderboard data. Returns the player or team Arm Strength leaderboard with verified year, team, position metric, minimum throws, local sort, and pagination filters. The player detail route returns individual throw records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoLocal sort field
typeNoLeaderboard row type
yearNoSeason or all years
limitNoRows per page (1-500)
offsetNoZero-based row offset
team_idNoMLB team id
positionNoPosition metric
sort_dirNoSort direction
min_throwsNoMinimum throws

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only restates that leaderboard/position/sort/pagination filters exist, without disclosing return format, default behavior (which row type is returned when 'type' is omitted), auth needs, or rate limits.

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?

Two sentences with the core purpose front-loaded and no obvious padding. The trailing 'player detail route' sentence is arguably unnecessary or misplaced for this leaderboard tool, slightly diluting focus.

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

Completeness3/5

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

For a 9-parameter tool with no annotations and no output schema, the description is adequate but leaves gaps: it doesn't say what the default row type is, how pagination defaults behave, or what fields the leaderboard rows contain. It covers the surface but not enough for confident invocation.

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%, so all 9 parameters are already documented in the schema with enums. The description's enumeration of filters adds no syntax or default-value meaning beyond what the schema provides, making the baseline of 3 appropriate.

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 ('Get') and resource ('Baseball Savant Arm Strength leaderboard data'), and it differentiates the leaderboard from a 'player detail route' that returns individual throw records. However, it is ambiguous whether that player-detail behavior lives in this same tool or in the sibling mlb_statcast_arm_strength_player, which muddies the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to select this tool over siblings like mlb_statcast_arm_strength_player, mlb_statcast_arm_angle, or mlb_statcast_arm_value. The mention of a 'player detail route' hints at a choice but never states the condition that selects 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