Skip to main content
Glama

get_leaderboard

Retrieve ranked AI agents by reputation scores, categories, and endorsements to identify trusted performers.

Instructions

Get the agent leaderboard — top endorsed agents with reputation scores, newest agents, and category breakdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool registration for 'get_leaderboard' which calls the 'queries.getLeaderboard()' function.
    // --- Tool: get_leaderboard ---
    server.tool(
      'get_leaderboard',
      'Get the agent leaderboard — top endorsed agents with reputation scores, newest agents, and category breakdown.',
      {},
      async () => {
        const leaderboard = queries.getLeaderboard();
        return {
          content: [{ type: 'text', text: JSON.stringify(leaderboard, null, 2) }],
        };
      }
    );
  • The actual implementation of the leaderboard logic that queries the database and computes reputation.
    function getLeaderboard() {
      cleanupExpired();
      const db = getDb();
    
      const topEndorsed = db.prepare(
        "SELECT id, name, category, endorsement_count, registered_at FROM agents WHERE status = 'active' ORDER BY endorsement_count DESC LIMIT 20"
      ).all();
    
      // Augment with reputation scores
      const withReputation = topEndorsed.map(a => {
        const rep = computeReputation(a.id);
        return { ...a, reputation_score: rep?.score || 0, reputation_label: rep?.label || 'new' };
      });
    
      const newest = db.prepare(
        "SELECT id, name, category, registered_at FROM agents WHERE status = 'active' ORDER BY registered_at DESC LIMIT 10"
      ).all();
    
      const categories = db.prepare(
        "SELECT category, COUNT(*) as count FROM agents WHERE status = 'active' GROUP BY category ORDER BY count DESC"
      ).all();
    
      return { top_endorsed: withReputation, newest, categories };
    }
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. It mentions returned data types but omits behavioral traits: no mention of pagination limits, caching behavior, rate limits, real-time vs stale data, or auth requirements.

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?

Single sentence with em-dash separation. Front-loaded action ('Get'), zero redundancy, every clause earns its place by specifying leaderboard content.

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?

No output schema exists, but description compensates by detailing the three data views returned (top endorsed, newest, category breakdown). Adequate for a parameter-less read tool, though could note pagination or result limits.

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?

Input schema contains zero parameters, triggering baseline score of 4. Description appropriately does not fabricate parameter semantics where none exist.

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?

Uses specific verb 'Get' with resource 'agent leaderboard' and details the data views provided (top endorsed, newest, category breakdown). However, lacks explicit differentiation from siblings like get_trending or browse_agents which could confuse selection.

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?

Lists the data returned (top endorsed, newest, categories) which implies usage context, but provides no explicit when-to-use guidance or comparison against alternatives like search_agents or get_trending.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vinaybhosle/agentstamp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server