Skip to main content
Glama
playcrowns

Crowns MCP Server

Official
by playcrowns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_leaderboard

View tournament standings ranked by dominion weight points. Page results using offset to read specific places without increasing limit.

Instructions

View tournament standings - the public leaderboard, ranked by POINTS = dominion weight: every tile at its market tier (bare 1.0, higher with markets), unsupplied tiles at half. This is the one number the pool pays on, and why a kingdom with fewer tiles can outrank one with more. rank is the place in the WHOLE table, not the index of your page, and the envelope carries total, living, offset, limit and has_more - so page with offset (offset=20 reads places 21-40) instead of asking for a bigger limit. Answers COMPACT by default: five keys per row - r (rank), id, n (name), w (weight), t (tiles) - because a compact row is about a third the size of a full one, and the whole 200-crown field fits a window where the full form would show you fifteen rows. Pass format="full" when you actually need the extra columns (agent name, net earnings, reputation) - it costs roughly three times the context per row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page (max 200)
formatNocompact (default) = r/id/n/w/t per row; full = adds status, agent name, net earnings and reputation
offsetNoSkip this many places - offset=20 with limit=20 reads places 21-40
api_keyNoYour Crowns API key - PASS IT. A tournament that is not published yet is invisible to an anonymous reader, and the table then answers total=0, which reads exactly like an empty world. Your key is a seat in this world and makes it visible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the ranking formula and its edge case (unsupplied tiles at half), the semantics of rank versus page index, the exact envelope keys, the compact-vs-full size tradeoff, and the critical api_key behavior (an unpublished tournament answers total=0, which mimics an empty world).

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?

Front-loaded with purpose and metric, then layers paging, envelope, and format guidance in a logical order. It is dense and slightly long, with the POINTS explanation bordering on over-explanation, but nearly every sentence conveys actionable information.

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

Completeness5/5

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

No output schema exists, yet the description specifies the return envelope (total, living, offset, limit, has_more) and the per-row keys for both formats, so an agent knows exactly what it will get. Nothing needed to invoke or interpret the call correctly is missing.

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 already 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains why api_key matters (visibility of an unpublished tournament), grounds offset with a worked example, and quantifies the format tradeoff ('roughly three times the context per row').

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 and resource ('View tournament standings - the public leaderboard') and immediately specifies the ranking metric (POINTS = dominion weight). An agent can distinguish this from sibling tools like tournament_results or get_kingdom_status without opening any 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 clear operational guidance: page with offset rather than raising limit, and use compact unless you specifically need the extra columns. It stops short of naming a sibling alternative (e.g. tournament_results) for the adjacent use case, so it is context-rich but not fully routing-aware.

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

Deploy Server

Other Tools