Skip to main content
Glama
Sign In

nibgate

by io.github.fortunesayspump
OverviewDiscussionsAdmin

get_leaderboards

Get ranked creators, sites, or content by reputation score, unlocks, views, and revenue (unlocks + tips + nibshares).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_leaderboards"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoPagination offset.
typeNoLeaderboard type (default creators).
limitNoMax results (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/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 implies a read-only ranking lookup but discloses nothing about auth requirements, rate limits, caching, or what the ranked output actually contains. The only added context is the definition of revenue as 'unlocks + tips + nibshares', which is a useful but narrow detail.

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?

A single front-loaded sentence stating the verb, resource, and metrics with zero filler. Nothing could be removed without losing information.

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?

For a zero-required-parameter read tool with no output schema and no annotations, the description covers purpose and the metric vocabulary but leaves return shape, pagination behavior, and operational constraints unaddressed. Adequate but with clear gaps.

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 skip, type, and limit are already documented with defaults and bounds. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 gives a specific verb ('Get') and resource ('ranked creators, sites, or content') and enumerates the ranking metrics (reputation score, unlocks, views, revenue). It is clear what the tool returns, though it does not distinguish itself from siblings like get_platform_stats or explore_content.

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 use this tool versus alternatives such as get_platform_stats or explore_content, and no mention of prerequisites or exclusions. Usage must be inferred entirely from the name and metric list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All nibgate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources