account_by_puuidLook up a Riot account (game_name, tag_line, puuid) by puuid via the regional Riot Account API (americas | europe | asia).
| Name | Required | Description | Default |
|---|---|---|---|
| puuid | Yes | ||
| region | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| puuid | No | Player UUID | |
| tagLine | No | Riot tag line | |
| gameName | No | Riot game name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false; description adds regional API detail but no additional behavioral traits like rate limits or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with essential info, but could be more structured (e.g., separating purpose and parameters).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple tool with output schema and annotations, description covers purpose, key fields, and regional limitation; no missing critical information for typical use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage 0% with no parameter descriptions; description mentions 'by puuid' and lists regions but does not detail parameter formats or constraints (e.g., puuid string format), partially compensating.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Look up a Riot account' with specific fields (game_name, tag_line, puuid) and distinguishes from sibling account_by_riot_id by specifying lookup key (puuid) and regional API.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Specifies regional scope (americas, europe, asia) and key (puuid), implying alternative account_by_riot_id for riot_id lookups, but lacks explicit when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.