Skip to main content
Glama

RankFuel Leaderboards

get_leaderboard

Public standings of a RankFuel leaderboard (radio listener board): station, contest, open/closed, ranked listeners (display names, towns, points; ties share a rank), and a ready-to-quote answer with the leader. Use when someone asks "who is winning/leading …" and has an rfwin.uk/lb/ link. No token needed. Free, no key.

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": {
      "boardId": "<boardId>"
    },
    "name": "get_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many places to return, 1-100 (default 10; listeners tied at the cutoff are included)
boardIdYesLeaderboard id (10 characters) or its public link, e.g. https://rfwin.uk/lb/abc123defg

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the whole burden and does real work: it declares the tool is public and free with no key or token, and it explains the result shape including tie semantics ('ties share a rank') and cutoff tie inclusion. What is missing is failure behavior — what happens for a wrong id, a private board, or a closed contest.

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 resource and payload, then the trigger, then the auth facts, which is the right order for an agent skimming. The first sentence is a long comma-delimited list that brushes against density, but every clause contributes information and nothing is redundant filler.

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-parameter read tool with no annotations and no output schema, the description covers the payload contents, tie semantics, and auth requirements, so return-value explanation is not needed. The remaining gap is error and edge-case behavior for a closed or nonexistent board, which the 'open/closed' field hints at but never explains.

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%, and the schema already documents both boardId (10-char id or public link) and top (1-100, default 10, ties at cutoff included). The prose adds nothing beyond that; the tie-handling note duplicates the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('Public standings of a RankFuel leaderboard') and enumerates exactly what the payload contains: station, contest, open/closed, ranked listeners with display names, towns, points, tie handling, and the leader. 'Public' plus 'no token needed' distinguishes it implicitly from the mutating siblings (create_leaderboard, close_leaderboard), so an agent can route without opening another 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 an explicit activation condition: when the user asks 'who is winning/leading …' and supplies an rfwin.uk/lb/<id> link. That is a concrete, checkable trigger. It stops short of naming an alternative or stating when not to use it (e.g., handling a private or closed board), so it is clear context without exclusions.

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