Skip to main content
Glama

LoL Player Index: player vs system value

invoke_lol_player_index
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. League of Legends Player Index, calculated by BankrollSZN: splits each player's DraftKings points per game (map) 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: Top, Jng, Mid, ADC, Sup. Seasons are splits: 20261 (to June), 20262 (July to September), 20263 (October on, Worlds). Extra: team name and league. Backtest split to split: error 3.22 vs 3.48 for a regressed last-split baseline. 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 March 2026 (LCK, LPL, LEC, LCS, internationals). 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_lol_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

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent safety profile, and the description goes well beyond them: provenance and model (Ridge on regular-season data since March 2026 across LCK/LPL/LEC/LCS/internationals), backtest error 3.22 vs 3.48 for a regressed baseline, and the approval prompt on first call. It stops short of describing response shape or refresh cadence, but that is a minor gap given the rich data-provenance context.

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?

Everything is packed into a single dense paragraph with no line breaks or grouping, so season-split rules, view modes and model provenance blend together. It opens with meta info about the approval prompt rather than the tool's job, weakening front-loading, though little of the content is genuinely wasted.

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 9-parameter, no-output-schema tool, the definition covers provenance, metric decomposition, season conventions, view selection and known accuracy. The main omission is that with no output schema, return-field shapes are only described loosely (metric names, archetype labels), leaving the agent to infer the payload.

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 adds real meaning the schema does not: view mode semantics and defaults, the season-split convention (20261 through June, 20262 July–September, 20263 October on incl. Worlds), and the group list. Sort fields and paging are left to the schema, which is acceptable.

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 states a specific resource and a specific analytic: splits DraftKings points per game into player_value, system_lift and residual, with trend, star with/without split, and archetype labels. Sibling differentiation is only indirect ('not a nightly projection'), but an agent can tell this is a retrospective player-vs-system ranking tool rather than a projection or pool 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?

It explains each view mode and its default: players (default; supply player for one player's season history), systems (team lift, latest season), and step_up (biggest gains when a team's star sits). It also signals the when-not case with 'not a nightly projection'. What's missing is an explicit named alternative (e.g. the projections sibling) to route agents that actually want a nightly number.

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