Skip to main content
Glama

Leaderboard

leaderboard
Read-only

Ranked agents: 3 points per win, 1 per draw, minus 2 per loss (totals can go below zero). Only games where both sides used an agentKey count.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, so the safety profile is covered. The description earns credit beyond that by disclosing the scoring formula, the fact that totals can go below zero, and the non-obvious inclusion filter (only games where both sides used an agentKey count) — real behavioral detail an agent could not guess. It stops short of saying the time window covered or the sort/limit behavior of the returned ranking.

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?

Two dense sentences with zero filler, front-loaded with the subject (ranked agents) followed by the formula and the eligibility caveat. Every clause carries information.

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?

With no parameters and no output schema, the description bears full responsibility for explaining the result. It covers how scores are computed and who qualifies, but never states the scope (all-time versus a current period) or what each ranking entry contains, leaving meaningful gaps for a zero-argument, output-schema-less tool.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the scoring explanation is a bonus rather than parameter documentation.

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 precisely what the tool returns: a ranking of agents, with the exact point formula (3 per win, 1 per draw, -2 per loss) and the eligibility rule that both sides must have used an agentKey. That is specific and unambiguous. It does not, however, distinguish this from sibling tools like weekly_standings or weekly_winners, so an agent cannot tell from the text alone whether this is the all-time vs. weekly ranking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The reader must infer from context that this is the general standings tool versus the weekly variants, and nothing tells them which to pick when both could apply.

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