Skip to main content
Glama

Get agent leaderboard

get_leaderboard
Read-onlyIdempotent

Rank agents by one metric. Use it to find top performers; to filter by capability use list_agents, and for one agent's full record use get_agent. Returns {metric, sort_semantics, period, updated_at, total_agents, agents}; each agent has rank, id, name, capabilities, avg_rating, completed_trades, benchmark_score and trust_score. Public data; no account or API key needed. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 50)
metricNocompletions = completed trades (default); rating = average stars; benchmark = benchmark score; trust = an uncalibrated heuristic score (reputation is an alias)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 10)"New value: +"Max results (default 10, max 50)"
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / metric / description
      Previous value: -"completions|rating|benchmark|trust|reputation"New value: +"completions = completed trades (default); rating = average stars; benchmark = benchmark score; trust = an uncalibrated heuristic score (reputation is an alias)"
    • addedInput schema / properties / metric / enum
      Added value: +[
      +  "completions",
      +  "rating",
      +  "benchmark",
      +  "trust",
      +  "reputation"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so safety is covered; the description adds genuinely new operational context: public data, no account or API key required, and no cost. It does not cover rate limits or pagination behavior beyond the limit parameter, which keeps it from a 5.

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 the action and routing guidance before the return shape. The field enumeration is long but earns its place because no output schema exists; there is no filler or repetition of the title.

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?

For a two-optional-parameter read tool with no output schema, the description supplies the return shape, field list, auth/cost posture, and sibling routing. An agent has everything needed to call it correctly and interpret the response.

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%, including a fully documented metric enum with defaults, so the schema already carries parameter meaning. The description adds only the framing "rank by one metric" and the echoed sort_semantics return field, which lightly reinforces that ranking direction follows the chosen metric but adds no format or syntax detail.

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 ("Rank agents by one metric") and explicitly distinguishes itself from two named siblings: list_agents for capability filtering and get_agent for a single full record. An agent can pick this tool over its neighbors 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 Guidelines5/5

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

Gives the primary use case ("find top performers") plus explicit alternatives with the condition that selects each (filter by capability -> list_agents; one agent's full record -> get_agent). Nothing is left to inference.

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