Skip to main content
Glama

MLB hitter matchup card: what a pitching staff allows to his batting hand

invoke_mlb_player_matchup
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. MLB player matchup card, calculated by BankrollSZN. What one defense allows per game to the player's position group (hitters with the same batting hand: DK points, hits, total bases, HR, R+RBI, walks, strikeouts; last 81 games) vs the league average, with rank (N = allows the most), next to the player's own per-game numbers, his last 5 games and his games against that team. Window: each defense's most recent games across seasons, so early-season samples are not tiny. No opponent = his next opponent on the slate. Example: player Kyle Schwarber, opponent COL.

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": {
      "player": "<player>"
    },
    "name": "invoke_mlb_player_matchup"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYesHitter name.
opponentNoOpponent abbreviation (COL). Default today's opponent. Needed in the off-season.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the first call triggers an approval prompt ('Added after you connected: the first call asks you to approve it'), the sample window is 81 games, defensive windows span seasons so early-season samples aren't tiny, and rank direction is defined (N = allows the most). Those are useful disclosures, though the approval-prompt sentence is confusingly worded and the return shape (per-game lines vs. aggregates) stays ambiguous.

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

Conciseness3/5

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

The description is front-loaded with the core purpose and the parenthetical stat list is efficient, but the opening meta-sentence about approval prompts is oddly placed and slows the agent's entry into what the tool does. The long nested parentheticals make it dense, and the 'Example' sentence at the end could be trimmed.

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, the description carries the burden of explaining returns, and it does so well: it specifies the stat set, the 81-game hitter window, cross-season defensive windows, league-average comparison, rank direction, and the three comparison blocks (own per-game, last 5, vs this team). What remains unclear is the exact presentation/units of the returned card, which keeps it short of a 5.

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%, so both parameters are already documented, and the description largely restates that (opponent defaulting to the next slate opponent, off-season requirement). It does add a concrete example ('player Kyle Schwarber, opponent COL') and clarifies that the opponent drives the defensive-split half of the card, but offers no abbreviation format rules or fallback behavior beyond what the schema says. Baseline 3 applies where the schema carries the weight.

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?

The description names a specific artifact — an MLB hitter matchup card — and enumerates exactly what it contains: what a defense allows to the player's batting-hand group (DK points, hits, TB, HR, R+RBI, BB, K, last 81 games) versus league average with a rank, alongside the player's own per-game numbers, last 5 games, and games vs that team. That is far more specific than a name restatement. It does not, however, explicitly distinguish itself from close siblings such as invoke_mlb_hitter_splits or invoke_mlb_matchup, leaving the agent to infer the boundary.

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 only implied: you call it for a hitter's matchup context against an opposing staff. The one conditional given — 'No opponent = his next opponent on the slate' and 'Needed in the off-season' — is parameter behavior rather than when-to-use-this-tool guidance. There is no statement of when to prefer this over hitter_splits or the generic matchup siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources