Skip to main content
Glama

get_chat_rankings

Read-only

Retrieve per-player chat rankings for a match, night, or time range, including counts, rates, and examples across teasing categories like swearing, complaining, and praise.

Instructions

All-chat rankings for friends to tease each other (a word list, NOT moderation - it misses sarcasm). Podiums: toxic ('boca suja': swearing), whine ('chorão': cheating accusations, luck, complaining), death_cry (whining or swearing within 20 s of his own death - the real cry-baby number), talker ('tagarela': who types the most lines, whatever they say; no examples), laugh ('risadinha'), nice ('gente boa': praise, gg), shouting (caps). Each podium entry has the count, the rate per round played and one or two example lines (slurs masked). players has every count per player.

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": "get_chat_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows of `players`.
nightNoOne night, YYYY-MM-DD (the evening it started; games after midnight belong to the night before). See list_nights.
sinceNoOnly matches played at or after this ISO 8601 moment.
untilNoOnly matches played before this ISO 8601 moment.
match_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds real behavioral context by disclosing that the classification is a word list that 'misses sarcasm' and that slurs are masked in examples. That tells the agent how far to trust the output, which is not encoded anywhere in structured fields. It does not state cost, ordering, or what an unfiltered call spans.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the purpose, then enumerates the podiums, then closes with return structure; each category gloss earns its place because the labels (death_cry, chorão, tagarela) are not self-explanatory. It is dense with parenthetical bilingual slang, which slows parsing slightly, but there is little filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description's return-value details are bonus rather than necessity, and the category definitions are genuinely needed. The gaps are the unexplained `match_id`, no statement of default scope when all date filters are null, and no routing relative to sibling stats tools, which leaves the agent guessing on a 5-parameter tool.

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

Parameters3/5

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

Schema coverage is 80%, so the baseline is 3. The description reinforces that `limit` sizes the `players` rows and that `players` carries every count per player, but it says nothing about `match_id`, the one parameter left undocumented in the schema, and does not clarify whether omitting all date filters means all-time.

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 scope: all-chat rankings organized as 'podiums' across named categories (toxic, whine, death_cry, talker, laugh, nice, shouting). It is unmistakably different from get_player_stats or get_rivalries in what it returns. It stops short of naming a sibling or stating a comparative purpose, so it is clear but not differentiating.

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?

Usage is only implied: the tool is for 'friends to tease each other' and is explicitly 'NOT moderation', which warns against a plausible misuse. There is no statement of when to call it versus get_player_stats, get_rivalries, or get_highlight, and no guidance on which filters (night vs since/until vs match_id) to combine.

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