Skip to main content
Glama

Riot Games

by io.github.pipeworx-io

Summoner By Puuid

summoner_by_puuid
Read-onlyIdempotent

Fetch LoL summoner details (summoner ID, account ID, summonerLevel, profileIconId, revisionDate) for a puuid on a specific platform (e.g. na1, euw1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
puuidYes
platformYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSummoner ID
nameNoSummoner name
puuidNoPlayer UUID
accountIdNoAccount ID
profileIconIdNoProfile icon ID
summonerLevelNoSummoner level

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false. Description adds value by specifying the exact fields returned, which is not in annotations. No contradictions.

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?

Single sentence, front-loaded with key information, no unnecessary words. Extremely concise and easy to parse.

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 simple fetch tool, description covers required inputs and returned fields. Output schema exists to detail return values. Could mention platform format or validation, but overall adequate.

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

Parameters2/5

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

Schema description coverage is 0%, so description must compensate. It mentions 'puuid' and 'platform' and gives example 'na1' but does not explain what puuid is or list valid platform values. Minimal additional meaning.

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?

Description clearly states verb 'Fetch', resource 'LoL summoner details', lists specific fields (summoner ID, account ID, summonerLevel, profileIconId, revisionDate), and specifies key parameters (puuid, platform). It differentiates from siblings like account_by_puuid by focusing on summoner details.

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?

Description implies usage context (for a puuid on a specific platform) but does not explicitly state when to use this tool versus alternatives (e.g., account_by_puuid, match_ids_by_puuid). No when-not or alternative 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