Skip to main content
Glama

RankFuel Leaderboards

add_points

Add (or with a negative number, remove) points for a listener on a RankFuel leaderboard. Needs the board id and its SECRET manage token. The listener is identified by public display name (+ optional town); a new name is added to the board automatically. PRIVACY: names are public, so use a first name plus last initial or a nickname; full names are shortened to "Jane S." and phone numbers or emails are rejected. Returns the listener's new total and rank and the top 10. 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>",
      "manageToken": "<manageToken>",
      "listener": "<listener>",
      "points": "<points>"
    },
    "name": "add_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoOptional town shown on the board; tells same-name listeners apart
pointsYesPoints to add, -1000..1000, not 0 (negative removes)
reasonNoOptional short label, e.g. call-in, trivia, check-in (max 24 characters)
boardIdYesLeaderboard id (10 characters) or its public link, e.g. https://rfwin.uk/lb/abc123defg
listenerYesPublic display name: first name + last initial, or a nickname/handle. No phone numbers or emails.
manageTokenYesSECRET manage token (rlb_…) returned once by create_leaderboard (the manage link also works). Keep private; never show it in public places.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that unknown names are auto-added to the board, that full names are shortened to 'Jane S.', that phone numbers/emails are rejected, what the response contains (new total, rank, top 10), and that there is no key or cost.

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 core action and its inverse, then prerequisites, then caveats. It is dense and nearly every sentence earns its place, though the PRIVACY clause partially restates the listener constraint already implied by the schema.

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?

A 6-parameter mutation with no annotations and no output schema is fully covered: inputs, identity model, side effects, privacy constraints, and return payload are all described. An agent could call this correctly without opening anything else.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: negative values remove points, the listener is keyed by public display name plus optional town, and new names are created automatically. The privacy normalization rule for the listener field is behavior the schema alone doesn't convey.

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 ('Add (or with a negative number, remove) points for a listener on a RankFuel leaderboard'), including the inverse operation. This clearly separates it from siblings like create_leaderboard, draw_winners, and get_leaderboard.

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 concrete prerequisites (board id plus SECRET manage token) and practical guidance on listener identity and privacy-safe naming. It doesn't explicitly name a sibling alternative or a when-not-to-use case, so it stops short of a 5.

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