Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_arm_strength_player

Get Baseball Savant arm-strength throw records for one MLB player by player ID, with optional season or all years, for performance analysis.

Instructions

Get Baseball Savant player throw details. Returns the individual Arm Strength throw records for one player, by positive player_id. year can be 2020 to 2026, or 9999 for all years, and defaults to the current verified season. Each throw has its year, fielder id, position, the measured arm-strength value and a play id.

Input Schema

NameRequiredDescriptionDefault
yearNoSeason or all years
player_idYesPositive MLB player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses useful traits: the return is individual throw records, the default is the 'current verified season', and 9999 means all years. It does not mention rate limits, auth requirements, or pagination, so the safety/operational profile remains thin.

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 with the core action, then scope, then parameter semantics, then return shape. Three sentences with little waste, though the opening 'Baseball Savant player throw details' is slightly redundant with the following sentence.

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 simple two-parameter read tool with no output schema, the description covers the input range, default behavior, and the fields each returned throw contains (year, fielder id, position, arm-strength value, play id). An agent has enough to invoke it correctly, though operational details like limits are absent.

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 description coverage is 100%, so the base is 3, but the description adds meaning beyond the schema: it specifies the valid enumeration range (2020 to 2026 or 9999 for all years) and the default (current verified season), which the schema's bare 'Season or all years' label does not convey.

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 states a specific verb and resource: 'Get Baseball Savant player throw details' and clarifies it returns 'individual Arm Strength throw records for one player'. It distinguishes the player-scoped nature of the tool implicitly, though it never names the sibling aggregate tool (mlb_statcast_arm_strength) to make the boundary explicit.

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?

The description implies usage via 'for one player, by positive player_id' and documents the year default, giving the agent enough to know it is a single-player lookup. However, it offers no explicit when-to-use vs when-not guidance and never points to an alternative tool for team-level or aggregated arm-strength data.

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