Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_game_play_by_play

Retrieves MLB game play-by-play by numeric game ID, returning each at-bat with inning, batter, pitcher, event, description, and pitch-level records for detailed analysis.

Instructions

Get MLB game play-by-play. Returns the at-bats of an MLB game by numeric id. Each play has its inning and half, batter, pitcher, event and description, and a list of individual pitch and event records with timing and pitch data. The response includes a total count of plays.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric MLB game id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/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. It does disclose the return shape in detail (each play's inning/half, batter, pitcher, event, description, nested pitch records, plus a total count), which is meaningful behavioral context for a read tool with no output schema. It omits any note on auth, rate limits, or pagination, so it only partly meets the no-annotation burden.

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, purpose front-loaded, then return details. Every sentence adds something, though the closing sentence about `total` is minor. No wasted padding.

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 single-id read tool with no output schema and no annotations, the description covers purpose and the structure of the returned plays well, which is what an agent needs to call it. It is only missing guidance on obtaining the game id and any sibling routing.

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 the single id parameter is already documented as 'Numeric MLB game id'. The description echoes 'by numeric id' without adding format, source, or lookup guidance, so it neither compensates for nor improves on the schema. Baseline 3 applies.

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 MLB game play-by-play') scoped by numeric id, and the return-content description (at-bats, pitches) distinguishes it from a generic game or boxscore tool. However, it never names the close siblings mlb_game or mlb_game_boxscore, so the agent must infer the split rather than being routed.

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 guidance, no conditions, and no mention of alternatives despite many mlb_* siblings. Usage is only implied by the name and the 'by numeric id' scoping.

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