Skip to main content
Glama

Riot Games

by io.github.pipeworx-io

Summoner Top Mastery

summoner_top_mastery
Read-onlyIdempotent

Highest champion mastery entries for one League of Legends account from the Riot Games API, given a puuid and a platform routing value such as na1, euw1, or kr, with count controlling how many champions come back (default 3). Returns championId, championLevel, championPoints, last play time, and chest and token flags for those champions. Answers which champions a League of Legends player has played most and mastered furthest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
puuidYes
platformYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesTop N champion mastery entries

TDQS

A4.6/5.0
Behavior4/5

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

The description discloses the default count of 3, the return fields (championId, championLevel, championPoints, last play time, chest/token flags), and the data source (Riot Games API). These go beyond the annotations' read-only/idempotent hints, providing concrete behavior without contradicting the annotations.

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?

The description is three sentences, front-loading the core purpose in the first sentence, then specifying return fields and the higher-level question answered. No filler words, and every sentence adds value.

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?

Given there are only 3 parameters, an output schema, and annotations covering safety, the description provides all necessary context: parameters, defaults, return fields, and use case. It is complete for an AI agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides zero descriptions for any of the three parameters, but the description compensates fully: it defines puuid as 'one League of Legends account', platform as 'platform routing value such as na1, euw1, or kr', and count as 'controlling how many champions come back (default 3)'. This gives complete semantic meaning for invocation.

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 resource ('highest champion mastery entries for one League of Legends account') with a clear verb ('Returns'), and includes the question it answers ('which champions a League of Legends player has played most and mastered furthest'). This distinguishes it from generic sibling tools like champion_mastery by emphasizing 'highest' and 'top mastery'.

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?

The description gives explicit invocation parameters (puuid, platform, count) and states the intended use case (answering most-played/mastered champions). However, it does not mention alternatives or when not to use, so it stops short of full usage guidance.

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

All Riot Games 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

B3.1/5.0
Disambiguation2/5

Several tools have overlapping purposes: champion_mastery and summoner_top_mastery both return mastery data, and the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) plus deep_research all handle question-answering. The inclusion of an entire unrelated Pipeworx research suite under a Riot Games server creates cross-domain ambiguity, making it difficult to know which tool to select.

Naming Consistency3/5

Most tools use snake_case, but the pattern varies: resource_by_key (account_by_puuid), verb_noun (generate_llms_txt, compare_entities), bare verbs (forget, recall, remember), and standalone nouns (match, status). Pipeworx and polymarket tools share consistent prefixes, but the Riot tools and meta-tools break the pattern, resulting in a mixed but still readable convention.

Tool Count2/5

42 tools is far above the typical 3-15 for a focused server. Only 10 are Riot Games-specific; the remaining 28 are unrelated Pipeworx, data-research, Polymarket, and memory tools. The excessive count dilutes the server's purpose and makes it feel bloated.

Completeness3/5

The Riot Games domain is covered reasonably well with accounts, summoners, mastery, matches, and rankings, but misses common endpoints like champion static data and live match info. The extensive non-Riot tools do not fill these gaps and instead add an unrelated, separately complete surface that distracts from the server's apparent purpose.

Resources