Skip to main content
Glama

MLB Player Index: player vs system value

invoke_mlb_player_index
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. MLB Player Index, calculated by BankrollSZN: splits each player's DraftKings points per 4 plate appearances (hitters) or per 25 batters faced (pitchers) into player_value (above an average player on an average team), system_lift (what the current team adds) and the rest, with a trend vs the season before, a star with / without split and an archetype: Difference maker, System product, Rising, Blocked by teammates, Fading, Neutral. Groups: H (hitters), SP (starters), RP (relievers). Extra: park effect, start rate over the last 10 and share of team games, plus the park coefficients (view parks). Backtest pitchers: error 3.54 vs 3.65 for a regressed last-season baseline; hitters 0.849 vs 0.856. Off-season: values are through the 2026 season. view players (default; give player for one player with season history), systems (team lift, latest season) or step_up (biggest gains when the team's star sits). Ridge model on regular season data since 2023. A ranking of who is real and who rides the team, not a nightly projection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "invoke_mlb_player_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation.
viewNoDefault players.
groupNoplayers view: only this group.
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
playerNoPlayer name, or part of a name.
sort_byNoplayers view sort. Default player_value.
sort_dirNoDefault desc.
archetypeNoplayers view filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds information the annotations cannot: a first-call approval prompt, plan limits stacked on top of the limit parameter, off-season data being through 2026, and the underlying ridge model on regular-season data since 2023. Backtest error figures lend credibility but are less operationally useful than the approval and plan-limit disclosures.

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 core definition leads, which is good, but the body is a long run-on that mixes metric definitions, model metadata, backtest numbers, and park-effect asides in a single paragraph. The opening approval note is front-loaded but competes with the purpose statement for the reader's attention.

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 nine-parameter tool with no output schema, the description does substantial work: it explains the returned metrics, the categorical labels, the views, and the data vintage. It stops short of describing row shape or pagination behavior beyond the offset/plan-limit hints already in the schema.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it explains what player_value and system_lift represent, expands the H/SP/RP groups into hitters/starters/relievers, defines each archetype label, and clarifies that step_up means gains when the star sits. It does not explain how sort fields like system_share or expected interact with views, leaving a modest gap.

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 names a specific analytical artifact (MLB Player Index) and enumerates exactly what it decomposes: player_value, system_lift, trend, star with/without split, and archetype. The closing line "A ranking of who is real and who rides the team, not a nightly projection" sharply separates it from the projection-oriented siblings such as invoke_mlb_projections.

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?

It spells out the three meaningful call modes: "view players (default; give player for one player with season history)", "systems (team lift, latest season)" and "step_up (biggest gains when the team's star sits)", so an agent knows which view to pick for which question. It also implies an exclusion (not a nightly projection) but never names a sibling to use instead for projections.

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