Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_active_spin

Fetch MLB pitcher Active Spin table rows from Baseball Savant by season, calculation method, pitch-count minimum, and throwing hand, with local sort and pagination.

Instructions

Get Baseball Savant Active Spin rows. Returns pitcher Active Spin table rows for the selected season/calculation method, minimum pitch count, and throwing hand. Table sorting and pagination are applied locally. The player search only highlights pitchers in the first-party SVG visualization; the SVG chart and CSV download remain outside this JSON table contract.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minNoMinimum total pitches
handNoPitcher throwing hand; omit for both
sortNoLocal table sort field
yearNoSeason and calculation method
limitNoRows per page (1-500)
offsetNoZero-based row offset
sort_dirNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/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, and it does disclose non-obvious behavioral boundaries: local sorting/pagination, the player search only highlighting pitchers in the SVG, and the SVG/CSV living outside the JSON contract. It still omits anything about read-only guarantees, rate limits, or result volume, hence not a 5.

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 SVG/CSV boundary caveat. Efficient overall, though the final sentence is somewhat tangential to purely invoking the tool.

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?

With no output schema and no annotations, the description must carry return-value context, and it does state that it returns pitcher Active Spin table rows with the applied filters and local sort/pagination. It gives an adequate but not detailed picture of the returned table's contents.

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 coverage is 100% and every parameter is self-documented with enums, so the baseline is 3. The description restates the main dimensions (season/method, min pitch count, hand) but adds no format or syntax meaning beyond what the schema already provides; the local-sort note is behavioral rather than parameter-level.

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 ('Get') and resource ('Baseball Savant Active Spin rows') and clarifies it returns pitcher Active Spin table rows scoped by season/calculation method, min pitch count, and throwing hand. Clear purpose, but it never differentiates itself from the many sibling mlb_statcast_* tools (pitch_arsenal, arm_angle, etc.).

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?

Usage is implied through scope statements ('sorting and pagination applied locally', 'the SVG chart and CSV download remain outside this JSON table contract'), which helps the agent understand boundaries. However, there is no explicit when-to-use this vs. sibling statcast tools, nor any stated prerequisite.

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