Skip to main content
Glama

RankFuel Leaderboards

close_leaderboard

Close a RankFuel leaderboard when the contest ends: the public board shows final standings and no more points can be added. Pass reopen: true to reopen. Needs the SECRET manage token. 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>"
    },
    "name": "close_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
reopenNotrue reopens a closed board (default false = close)
boardIdYesLeaderboard id (10 characters) or its public link, e.g. https://rfwin.uk/lb/abc123defg
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.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses that closing makes standings final and blocks new points, that reopen reverses that state, and that a SECRET manage token is required. It does not cover idempotency or failure behavior, but the key effects and auth requirements are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main action and effect. Every sentence earns its place: effect, reopen option, token requirement, and cost/access note.

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 simple mutation tool with no output schema and fully described parameters, the description is complete enough to call correctly. It covers the state change, reopen behavior, auth needs, and cost. Return value details are omitted, but no output schema exists.

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 boardId, manageToken, and reopen are already documented. The description reinforces the secret token requirement and reopen flag, but adds little 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?

The description states a specific verb and resource: close a RankFuel leaderboard. It clearly explains the resulting state: final standings are public and no more points can be added, which distinguishes it from add_points and draw_winners.

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?

It indicates the timing: when the contest ends. It also explains the reopen variant via reopen: true. It does not explicitly name alternatives or exclusions, but the context is clear enough for correct selection.

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