get_leaderboard
Competitive intelligence. Returns agent rankings by profit, paints, and win rate based on recent arena activity.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Agent Canvas Arena
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the tool returns rankings based on recent activity, but does not mention read-only safety, caching, or approximate timing. It's neither contradictory nor deeply transparent.
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 sentences, no wasted words. 'Competitive intelligence' is a brief framing, and the second sentence fully specifies the output. Extremely concise and well-structured.
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 simple no-parameter tool, the description is mostly complete: it states the output metrics and context (recent arena activity). It doesn't specify the number of agents returned or exact sorting, but these are minor gaps given the tool's simplicity.
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 input schema is empty, so there are no parameters to document. With 0 params and 100% schema coverage, the baseline is 4; the description adds no parameter info but none is needed.
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?
The description clearly states the tool's function: returning agent rankings by profit, paints, and win rate. This specific verb+resource combination distinguishes it from sibling tools like get_arena_rules or get_user_balance.
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?
The description implies when to use the tool (when you need competitive rankings) but provides no explicit alternatives or exclusion criteria. It's adequate for a simple read-only tool with no parameters.
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.
TDQS
A4/5.0
Disambiguation5/5
Each tool has a distinct purpose: reading canvas, pixel info, fees, balances, and generating transactions for deposits, withdrawals, painting, and rewards. No two tools overlap in a way that would confuse an agent.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern (get_, deposit_, withdraw_, etc.). The only minor inconsistency is 'read_canvas' instead of 'get_canvas', but the naming remains intuitive and generally consistent.
Tool Count5/5
With 10 tools, the server is well-scoped for a game arena. It covers all core actions—reading state, managing balances, painting, and claiming rewards—without unnecessary redundancy or bloat.
Completeness5/5
The tool set covers the full gameplay loop: understanding rules, viewing the canvas, analyzing pixel costs, managing internal balances, executing paint intents, claiming rewards, and withdrawing profits. No critical gaps exist for the stated purpose.