Skip to main content
Glama

Mlb Stats

by io.github.pipeworx-io

Mlb Player Game Log

mlb_player_game_log
Read-onlyIdempotent

MLB player GAME LOG — per-game batting or pitching lines for a season, newest first, from the official MLB Stats API. "How has Yordan Alvarez hit over his last 10 games", "Gerrit Cole's last five starts", " recent form". Accepts a player NAME (resolved automatically) or numeric person_id; defaults to the current season and the most recent 15 games. Each row carries the date, opponent, home/away, game result, gamePk, and the line (hitting: AB, H, HR, RBI, BB, K, SB, plus running AVG/OPS; pitching: IP, H, R, ER, BB, K, HR, pitches, decision).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lastNoHow many most-recent games to return (default 15, max 200). The full-season count is always reported in games_in_season.
groupNoOptional "hitting" or "pitching". Defaults to hitting for position players and pitching for pitchers.
playerYesPlayer NAME (e.g. "Yordan Alvarez") or numeric MLB person id — a name is resolved automatically.
seasonNoSeason year, e.g. 2025. Defaults to the current season.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the data source, newest-first ordering, automatic name resolution, season/default-game-count behavior, and the exact fields returned in each row. No contradictions with the annotations; it adds substantial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four focused sentences: definition, example triggers, invocation contract, and return-field breakdown. Every sentence adds value, and the most important scoping ('per-game', 'newest first') is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing return values, and it does so thoroughly by enumerating date, opponent, home/away, result, gamePk, and hitting/pitching line fields. Defaults, accepted identifiers, and intended queries are all covered.

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 the baseline is 3. The description reinforces automatic name resolution, default season, and default group behavior, but these are already in the schema; no additional parameter semantics are needed.

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?

The description states a specific, unambiguous purpose: per-game batting/pitching lines for an MLB player, newest first, from the official MLB Stats API. This clearly differentiates it from sibling tools like mlb_schedule, mlb_standings, and mlb_player_stats by focusing on game-level logs rather than aggregates or fixtures.

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?

Natural-language examples ('How has Yordan Alvarez hit over his last 10 games', 'Gerrit Cole's last five starts') give clear context for when to invoke the tool. It stops short of explicitly naming alternatives or saying when not to use it, so it earns a strong four rather than a five.

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

All Mlb Stats toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Severe overlap between entry points: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and the prediction-market cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk) has fuzzy boundaries that would confuse an agent picking one. Entity lookups (entity_profile, compare_entities, recent_changes, validate_claim) also overlap on company data. The stakes are raised by the server being named 'Mlb Stats' while most tools are unrelated general-data tools, compounding misselection risk.

Naming Consistency2/5

There is internal consistency within families — the 7 MLB tools share a clean get_ prefix, and the Poly tools share a polymarket_ prefix — but the overall set mixes bare verbs (remember, recall, forget), prefixed families (ask_pipeworx_*), and descriptive compounds (ai_visibility_check, generate_llms_txt) with no unifying convention. The 'Mlb Stats' server name bears no relation to the dominant ask_pipeworx/deep_research naming, which further breaks pattern expectations.

Tool Count2/5

38 tools is well past the heavy threshold, and more importantly the bulk of them (SEC filings, FRED economics, Polymarket arbitrage, npm scanning, AI visibility, subscriptions) have nothing to do with the server's stated MLB purpose. Only 7 of 38 tools are actually baseball-related, so the count is both too high for the labeled scope and misallocated.

Completeness3/5

The 7 MLB tools cover teams, rosters, schedule/scores, standings, player profiles, season stats, and batter-vs-pitcher history — a solid read-only core. However, obvious gaps remain: no per-game box scores, no league leaders, no team offensive/pitching stats, no live game detail beyond final scores. The Pipeworx catch-all router technically fills data gaps but leaves the MLB-specific surface incomplete.

Resources