Skip to main content
Glama

ShowMRR

MRR leaderboard

get_leaderboard
Read-onlyIdempotent

Startups ranked by current MRR, optionally within one category or verified-only. Each row says whether its MRR is verified or self-reported.

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_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNoCategory name, e.g. "saas" or "ai".
verified_onlyNoOnly startups whose MRR is verified from a connected payment provider.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Category name, e.g. \"saas\" or \"ai\". Use list_categories to see the categories that exist."New value: +"Category name, e.g. \"saas\" or \"ai\"."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely new context: each row carries a verified vs self-reported flag, which matters for trusting the numbers and is not derivable from annotations.

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?

Two short sentences, with the core ranking behavior front-loaded and the filter options and row semantics following. No redundant or filler wording.

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?

With no output schema, the note that rows disclose verification status fills an important gap for a ranking tool. The remaining omission is minor: sort direction (presumably descending MRR) and tie-handling are left implicit.

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 coverage is 67%; both category and verified_only already have schema descriptions and limit carries its default and 1-25 bounds. The description only reinforces that the category filter is a single optional value, adding little beyond the schema. Baseline 3 is appropriate.

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 names a specific resource and operation: startups ranked by current MRR, with optional category and verified-only narrowing. That ranking framing distinguishes it from get_mrr_history (a per-startup time series) and search_startups (a text search), though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The phrase 'optionally within one category or verified-only' tells the agent these filters exist and are optional, which implies when to apply them. It never states when to prefer this tool over get_mrr_history or compare_startups, and offers no exclusion guidance.

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