Skip to main content
Glama

get_challenge_leaderboard

Read-only

Ranking for one challenge: each participant's rank and workout days logged in the window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "challengeId": "<challengeId>"
    },
    "name": "get_challenge_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
challengeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a safe read (readOnlyHint=true) against a closed domain (openWorldHint=false), so the description needn't restate safety. It does add that the payload is per-participant rank plus logged workout days, but 'in the window' is never defined (challenge window? trailing period?) and no ordering or pagination behavior is disclosed.

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 compact sentence that front-loads the resource and enumerates the returned fields with no filler. The trailing clause 'in the window' is under-specified rather than wasteful, a minor blemish on an otherwise efficient statement.

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

Completeness3/5

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

With no output schema, the description usefully sketches the return shape (rank, workout days), which is a real contribution. However, for a tool keyed solely by an undocumented challengeId it leaves gaps: what 'the window' means, behavior on unknown/inactive challenges, and whether unranked participants appear.

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 0% for the single challengeId parameter, but the description's phrase 'for one challenge' at least signals the parameter's role and that exactly one challenge is scoped per call. It adds no format details (ID type, source) beyond that, which is thin compensation for the coverage gap.

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?

The description names a specific resource (ranking/leaderboard for one challenge) and states the returned fields (each participant's rank and workout days logged), so the agent understands what it fetches. It omits an explicit verb but the intent is unambiguous and no sibling tool covers leaderboards.

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 guidance on when to call this versus other challenge tools (e.g., create_challenge, delete_challenge, set_challenge_active), nor any preconditions such as whether the challenge must be active or the caller enrolled. Usage must be inferred entirely from the name.

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.