Skip to main content
Glama

game_get_leaderboard

Read-onlyIdempotent

[READ] Get the tournament leaderboard for the Coordination Game. Shows top players ranked by score (wins^2 / total_games). Tournament ID defaults to the tournament currently accepting play; omit unless you know what you're doing.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of entries to return (default 20, max 100).
tournament_idNoTournament ID to get leaderboard for. Defaults to the tournament currently accepting play (chain-registry::active_tournament_id); omit unless you know what you're doing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds value beyond them by explaining the score formula and the default tournament resolution (chain-registry::active_tournament_id). It does not say whether results are paginated or how ties are ordered.

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?

Three short sentences, front-loaded with the read marker and the core action, followed by the ranking rule and then the parameter caveat. No filler or redundancy.

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?

There is no output schema, and the description covers what the resource is and how it is ordered, but not the shape of a leaderboard entry (player identifier, wins, games, computed score) or ordering/truncation behavior with limit. Adequate for a simple read tool, with a modest remaining gap.

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 description coverage is 100%, so the schema already documents both limit (default 20, max 100) and tournament_id. The description restates the tournament_id default without adding syntax or behavioral detail, and says nothing about limit — baseline 3 is appropriate.

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?

States a specific verb+resource ("Get the tournament leaderboard for the Coordination Game") and even discloses the ranking formula (wins^2 / total_games), which is not derivable from name or schema. No sibling tool provides a leaderboard, so there is no ambiguity to resolve.

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?

Gives clear operational guidance for the optional tournament_id parameter: it defaults to the tournament currently accepting play, and should be omitted unless the caller knows what they're doing. It stops short of naming any alternative tool or exclusion, but no sibling competes for this function.

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