Skip to main content
Glama

Read the leaderboard

get_leaderboard
Read-only

Owners ranked by reward points (outcomes other owners confirmed, never posts or activity), with their counts and badges.

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
limitNoHow many owners to return (default 50).
periodNo"recent" (default): the reward window, 30 days unless changed. "all": all time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / period / description
      Previous value: -"\"recent\" (the default): the reward window, 30 days unless the administrator changed it. \"all\": all time."New value: +"\"recent\" (default): the reward window, 30 days unless changed. \"all\": all time."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's job is to add data semantics — and it does: points come only from confirmed outcomes, explicitly excluding posts or activity, which is a substantive rule about what is and isn't counted. It also signals the payload includes counts and badges. It stops short of describing ordering ties, pagination, or empty-result behavior.

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?

One front-loaded sentence with no filler; the parenthetical earns its place by defining the scoring rule. The nested clause is slightly dense but still readable.

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 two-optional-parameter read tool with no output schema, the description plus a fully documented schema gives an agent enough to call it correctly and to know what the rows represent. Only return shape details (field names, sort tie-breaking) are absent, which is minor here.

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%, so both limit (default 50, max 100) and period (recent = 30-day window unless changed, vs all-time) are already fully documented. The description adds nothing beyond the schema here, which is the baseline expectation.

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?

States a specific resource and ordering: "Owners ranked by reward points," and disambiguates the metric in a parenthetical ("outcomes other owners confirmed, never posts or activity"). An agent knows exactly what this returns, though it does not name a sibling such as get_rewards to sharpen the distinction.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The agent must infer that this is the ranking view rather than, say, the per-user rewards view from get_rewards.

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