Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_run_value

Retrieve MLB Baseball Savant batting or pitching Run Value rows from the Swing-Take leaderboard, filtered by season, team, plate appearances, or leverage. Supports sorting and pagination.

Instructions

Get Baseball Savant Run Value rows. Returns batting or pitching Run Value rows from the Swing-Take leaderboard. Filters are cold-replay verified; sorting and pagination are applied locally. The Bat-side R/L selector was verified to leave the embedded rows byte-identical and is omitted. The page's visual charts and CSV export are separate formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minNoMinimum plate appearances
sortNoLocal table sort field; supported set varies by view
teamNoMLB numeric team id; omit for all teams
typeNoTable view
yearNoSeason, All, or Career
groupNoRow group
limitNoRows per page (1-500)
offsetNoZero-based row offset
leverageNoRun-value method
sort_dirNoSort direction
sub_typeNoConditional subtype: Swing/Take; pitch name; or Heart/Shadow/Chase/Waste

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/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 useful work: it discloses that sorting and pagination are applied locally (not server-side), that filters are 'cold-replay verified', that the Bat-side R/L selector is omitted because it leaves rows byte-identical, and that charts/CSV export are separate formats. These are non-obvious behavioral traits. It stops short of 5 because permissions/rate limits and return shape are untouched.

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?

Four front-loaded sentences with the purpose first, then scope, then behavioral caveats. Dense but each sentence carries information; jargon like 'cold-replay verified' and 'byte-identical' is a minor readability cost rather than padding.

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 an 11-parameter tool with no annotations and no output schema, the description covers behavioral scoping well and mentions the return subject ('Run Value rows'), but leaves the actual returned fields and pagination semantics of the output implicit. Adequate but with visible gaps given the tool's complexity.

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 beyond the schema: it clarifies that sort/sort_dir and limit/offset act locally rather than server-side, and explains why a Bat-side selector parameter is absent. That extra interpretation lifts it above baseline.

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 Run Value rows') and scopes it to batting or pitching rows from the Swing-Take leaderboard, which separates it from sibling statcast tools like fielding_run_value and arm_value. It does not name a sibling explicitly, so it falls short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description never tells an agent how to choose this tool over the many other mlb_statcast_* siblings, nor what prerequisites exist. Context is implied only through the leaderboard scope.

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