Skip to main content
Glama

Revenue leaderboard (ranked)

leaderboard
Read-onlyIdempotent

Use when the user asks which AI agents or AI startups make the most money, or for a top-N revenue ranking. Returns businesses ranked by latest sourced annualized revenue, highest first (same briefs, with verification_label, as search_businesses). Example: {"category":"coding-agents","limit":5} -> the top 5 coding agents by revenue. Use it for a pure ranking or top-N, optionally per category or verified_only (limit max 50); it has no keyword search, use search_businesses for that. Cost: free (100 calls/day without a key).

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": "leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, max 50.
categoryNoCategory slug, e.g. coding-agents (see list_categories).
verified_onlyNoKeep only businesses whose headline figure is payment-processor verified (headline_verification not null).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Category slug, e.g. coding-agents (see list_categories)."
    • addedInput schema / properties / limit / description
      Added value: +"Default 10, max 50."
  2. Changed5 schema fields changed
    • addedOutput schema / properties / result / items / properties / referral
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / result / items / properties / signup_go_url
      Added value: +{
      +  "description": "Same link via mrrledger.com/go/<slug> (counts the click, then 302)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / items / properties / signup_url
      Added value: +{
      +  "description": "Referral link (only on businesses with one). Always shown with signup_url_disclosure; never affects figures, ranking, sorting or verification.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / items / properties / signup_url_disclosure
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / items / properties / signup_url_label
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, safe profile; the description adds real value beyond them with cost/rate-limit information (free, 100 calls/day without a key), sort order, and the note that results carry the same briefs and verification_label as search_businesses. It stops short of describing response-size or pagination behavior, but the output schema covers the return shape.

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 trigger condition and the sibling exclusion, and every sentence carries information (example, constraints, cost). It is dense as a single paragraph, but there is 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?

With only three optional, fully documented parameters, a present output schema, and annotations covering safety, the description supplies everything an agent needs: when to call, what it returns, sorting, limits, cost, and the alternative for keyword search.

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 100%, so the baseline is 3; the description adds a concrete example call ({"category":"coding-agents","limit":5}) and reinforces the limit max of 50 and per-category scope, giving the agent more than the schema alone.

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: returns businesses ranked by latest sourced annualized revenue, highest first. It explicitly distinguishes itself from search_businesses ('it has no keyword search, use search_businesses for that'), so an agent can route between the two without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with the triggering user question ('which AI agents or AI startups make the most money') and names the alternative tool for the keyword-search case. The exclusions are explicit and actionable.

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