Crawlora MCP

mlb_player_stats

Read-only

Returns one player's MLB season statistics. The group enum accepts every value returned by mlb_discovery. id: Required. Numeric MLB player id. end_date: Optional. Date-range end for byDateRange stat types; must be paired with start_date. Use mlb_player to get an MLB player.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "group": "<group>"
    },
    "name": "mlb_player_stats"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric MLB player id.
`group`	Yes	Required. One of hitting, pitching, fielding, catching, running, game, team, streak.
`season`	No	Optional. Four-digit season; defaults to the current year.
`end_date`	No	Optional. Date-range end for byDateRange stat types; must be paired with start_date.
`game_type`	No	Optional. MLB game type code.
`stat_type`	No	Optional. One of the stat types accepted by this endpoint; defaults to season.
`start_date`	No	Optional. Date-range start for byDateRange stat types; must be paired with end_date.
`opponent_team_id`	No	Optional opposing team id; required by vsTeam stat types.
`opponent_player_id`	No	Optional opposing player id; required by vsPlayer stat types.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no context on permissions, rate limits, or data freshness, and an output schema exists to cover the return shape, so it neither contradicts nor enriches the behavioral picture significantly.

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?

Reasonably short and front-loads the core purpose before parameter notes and the sibling pointer. Slightly choppy with inline 'id: Required' fragments that duplicate the schema rather than earning their place.

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 read-only stats tool with a full output schema and annotations, the description covers purpose, a cross-reference for the group enum (mlb_discovery), and basic parameter notes. Completeness is adequate, though it does not explain stat_type or game_type options that the schema leaves open.

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%, so parameters are already fully documented. The description only repeats 'id: Required' and the end_date/start_date pairing, which is already stated in the schema for both fields; it adds no enum values or format details beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns one player's MLB season statistics'), scoping to a single player and one season. It also names a sibling (mlb_player) for identity lookup, letting an agent distinguish this stats tool from the player-lookup tool.

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?

Provides a clear routing rule ('Use mlb_player to get an MLB player') so the agent knows this tool is for stats after resolving identity. However, it does not distinguish itself from other stats-oriented siblings like mlb_league_stats or mlb_team_stats, leaving some ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?