Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_arm_value

Retrieve MLB Statcast extra bases run value leaderboard data for arm value, including filters, sorting, and pagination to compare player and team fielding performance.

Instructions

Get Baseball Savant Extra Bases Run Value leaderboard data. Returns the Arm Value section's complete embedded table, including its Run, Fld, Pit, team, and league views, filters, local sorting, and pagination. Expanded player rows are available from mlb-statcast-arm-value-details. The JSON rows contain the same selected records as the upstream CSV export.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoCase- and accent-insensitive local substring on the displayed row name; up to 100 characters
sortNoLocal table sort field
typeNoLeaderboard view
limitNoRows per page (1-500)
splitNoReturn one row per season
offsetNoZero-based row offset
team_idNoMLB team id from mlb_discovery, split for All Teams Split by Team, or empty for All Teams
end_yearNoEnd season, 2016 through current season; must be >= start_year
sort_dirNoLocal sort direction
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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden, and it does disclose non-obvious traits: it returns the complete embedded table with all views, filters, local sorting, and pagination, and that JSON rows mirror the upstream CSV export. It does not cover auth, rate limits, or error behavior, so the disclosure is useful but partial for a 14-param 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 sentences, front-loaded with purpose, then scope, then the sibling pointer. Little waste, though the final sentence about CSV parity is somewhat marginal. Efficient overall.

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 14-parameter, no-annotation, no-output-schema tool, the description covers the return shape at a high level (embedded table, CSV-equivalent JSON). It is adequate but thin: it does not describe row contents, what to expect when a filter yields nothing, or how the enumerated views interact.

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% and all 14 parameters carry their own descriptions, so the schema does the heavy lifting. The description adds no parameter-level semantics (e.g., it never mentions q, sort, split, or team_id), so the baseline 3 is 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?

States a specific verb and resource: 'Get Baseball Savant Extra Bases Run Value leaderboard data' and the 'Arm Value section's complete embedded table.' It also names the sibling mlb-statcast-arm-value-details, so the agent can distinguish the two. Minor ambiguity between the tool name (arm_value) and the described dataset (Extra Bases Run Value) keeps it from a 5.

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 points to mlb-statcast-arm-value-details as the place for 'Expanded player rows,' which gives a concrete routing alternative. However, there is no explicit statement of when to use this tool versus the details variant beyond that single hint, and no exclusions or prerequisites. Usage is implied rather than spelled out.

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