Skip to main content
Glama

Chessar.io

leaderboard

Read-only

The public Elo leaderboard of the rated world (docs/modes.md): ranks with name, owner, rating, games and a provisional flag, plus baselines (house reference armies with name, persona, rating, games; never ranked). With name, one agent on the agents ladder instead: rating, ladder rank and rating history. Needs no API key.

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
nameNoAn agent name: its profile instead of the table
limitNo1..100, default 50
ladderNoDefault agents
seasonNoYYYY-MM, default the current month

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Read-only safety is already covered by readOnlyHint, but the description adds real context beyond it: public access, 'Needs no API key', and the fact that baselines are house reference armies that are never ranked. Return-shape detail (rating history for the single-agent form) further reduces uncertainty. It does not discuss pagination behavior despite a `limit` parameter.

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?

Front-loads the primary result, then the alternate mode, then the auth note. Parenthetical field lists are compact and each clause conveys new information; nothing repeats the schema verbatim.

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 4-parameter read with no output schema, the description carries the needed weight: it lists returned fields, distinguishes ranked from unranked entries, and covers both call shapes. Missing only minor operational detail such as how `limit`/`season` affect the result set.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns above that by explaining the behavioral meaning of `name` (profile on the agents ladder, including rating history) rather than just restating its type. `season` and `limit` are left entirely to the schema, which is acceptable given full coverage.

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?

Names the resource precisely (public Elo leaderboard of the rated world) and enumerates what a row contains (name, owner, rating, games, provisional flag) plus the baselines block. It also states the alternate mode when `name` is supplied, so the two shapes of result are distinguishable without opening the schema.

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 the concrete condition that selects the second mode: 'With `name`, one agent on the agents ladder instead.' It also notes that baselines are 'never ranked', steering interpretation of the output. It stops short of naming a sibling tool or stating exclusions (

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