Skip to main content
Glama

RankFuel Leaderboards

create_leaderboard

Create a free RankFuel leaderboard (rnkfl.com) for radio listeners, no account needed: a public board for an on-air contest (call-ins, trivia, check-ins). Returns the public board URL, studio-screen URL and website embed (URL + iframe HTML), plus a SECRET manage token/URL in the "secret" block: give it only to the person running the board, never post it. Limits: 5 new boards per 10 minutes and 20 per day per connection; up to 500 listeners per board. 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": {
      "station": "<station>",
      "contest": "<contest>"
    },
    "name": "create_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoOptional brand colour as hex, e.g. #e65208 (default #3dd879)
contestYesContest name, e.g. "Summer Trivia" (max 80 characters)
logoUrlNoOptional https:// link to the station logo image
stationYesStation name or call sign, e.g. "CFAX 1070" (max 80 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it enumerates the returned artifacts (public board URL, studio-screen URL, embed URL + iframe HTML), flags the sensitive SECRET manage token in the 'secret' block with handling instructions, and discloses rate limits (5/10 min, 20/day) and the 500-listener cap.

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-loads what the tool creates and what it returns before the limits, which is the right ordering. The sentences are dense and semicolon-heavy, but each carries distinct operational value with no filler.

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 creation tool with no output schema and no annotations, the description covers everything an agent needs: what it returns, the sensitive-token handling rule, quotas, and listener caps. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all four parameters are already documented in the schema, so the baseline would be 3. However, the description adds non-obvious framing (public/on-air context, no account needed) that informs how station/contest values are chosen. Hmm — the description does not actually explain any parameter meaning beyond the schema.

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 (Create) plus the resource (RankFuel leaderboard) and narrows the domain to radio listeners with concrete use cases (call-ins, trivia, check-ins). An agent can distinguish it from get_leaderboard or close_leaderboard at a glance.

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 clear conditions for use ('public board for an on-air contest', 'no account needed') and the free/no-key precondition. It does not explicitly name the sibling tools to use for subsequent read/close/draw operations, so routing away from this tool is only implied.

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