Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_statcast_catcher_throwing_details

Retrieve per-attempt catcher throwing play records by supplying a catcher entity_id, with optional year, team, target base, and pagination filters.

Instructions

Get Catcher Throwing attempt details. Returns per-attempt play records expanded from a Catcher Throwing catcher row. Supply the entity_id from a Cat row and the row's year/team when it represents a season or team stint. Details are ungrouped source attempts, paginated locally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoEmpty, split, or team id from the corresponding leaderboard row
yearNoSeason
limitNoRows per page (1-500)
splitNoSplit rows by season
offsetNoZero-based row offset
minimumNoMinimum steal attempts
entity_idYesPositive catcher id from a Cat row
game_typeNoGame type
target_baseNoThrow target
with_team_onlyNoTeam roster membership filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add two useful traits: results are 'ungrouped source attempts' and pagination is done 'locally'. It does not state read-only nature, auth requirements, or expected result size, so behavioral disclosure is partial for a 10-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?

Four tight sentences, front-loaded with the purpose before the invocation mechanics. No filler, though the phrasing 'expanded from a Catcher Throwing catcher row' is slightly awkward jargon-heavy.

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 10-param, no-annotation, no-output-schema tool the description covers purpose, the key parent-row linkage, and pagination behavior. It omits filter semantics for limit/offset/minimum/split beyond what the schema already provides, but nothing critical to calling it correctly is missing.

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 already 100%, so baseline is 3. The description earns extra credit by explaining the semantic interplay between entity_id, year, and team (team/year matter only when the row represents a season or team stint), which the short schema descriptions only hint at.

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 concrete verb+resource (get Catcher Throwing attempt details) and clarifies the output is per-attempt play records expanded from a catcher row, which distinguishes it from the aggregate leaderboard sibling. It doesn't name the parent tool (mlb_statcast_catcher_throwing) explicitly, so the sibling differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear usage context: supply the entity_id from a Cat row plus the row's year/team when it represents a season or team stint. This tells the agent how to invoke it in the drill-down flow, but it never explicitly names the upstream tool or states when NOT to use this (e.g. use the leaderboard tool for a first lookup).

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