Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_arm_value_details

Retrieve game-level play details for a Baseball Savant Arm Value player row. Pass leaderboard filters to expand Run, Fld, or Pit player plays.

Instructions

Get expanded Baseball Savant Arm Value player plays. Returns the game-level play details displayed when expanding a Run, Fld, or Pit player row in the Arm Value leaderboard. Pass the leaderboard filters used to produce the selected row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoPlayer view
splitNoSplit leaderboard records by season
team_idNoMLB team id from mlb_discovery, split, or empty
end_yearNoEnd season, 2016 through current season; must be >= start_year
entity_idYesPositive player id from an Arm Value player row
game_typeNoGame type
start_yearNoStart season, 2016 through current season
key_base_outNoBaserunner situation
minimum_oppsNoMinimum opportunities
with_team_onlyNoTeam-roster membership for a selected team

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?

With no annotations, the description carries the full burden. It discloses what the return contains (game-level play details for a selected player row), which is genuinely informative, but omits any auth, rate-limit, or pagination behavior. Adequate but limited for a 10-parameter data tool.

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 tight sentences, front-loaded with the purpose and followed by the return content and the filter instruction. No wasted wording, though the sentence on the leaderboard expansion is slightly redundant with the first.

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 details sub-tool with no output schema and a fully documented 10-param schema, the description covers purpose, provenance (must come from a leaderboard row), and return content. It could be stronger by naming the parent leaderboard tool to close the workflow loop.

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% with 10 well-documented enum params, so the schema does the heavy lifting (baseline 3). The description adds only the instruction to reuse the leaderboard's filters, which is marginal value beyond the schema.

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 expanded Baseball Savant Arm Value player plays') and clarifies it returns the game-level details behind a leaderboard row. It implicitly distinguishes itself from the parent mlb_statcast_arm_value leaderboard sibling by describing the row-expansion relationship, though it never names that sibling directly.

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?

'Pass the leaderboard filters used to produce the selected row' implies the prerequisite (you must first have a leaderboard row and its filters), which is useful context. However, it never explicitly names mlb_statcast_arm_value as the source, nor states when-not to use this versus another details 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