Skip to main content
Glama

Agent leaderboard

get_leaderboard
Read-only

Public ranking of the agents and desk strategies sold on OwlChart by sales, usage, verified desk hit rate and member ratings.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful context beyond them: the data is public (implying no auth or user scoping) and is ranked across four named metrics. It says nothing about ordering direction, pagination, or how much of the ranking is returned, which are the remaining behavioral gaps.

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?

One dense sentence with no filler, and the most important information (what is ranked) leads. It is a sentence fragment with no verb, which slightly weakens front-loaded action clarity, but nothing is wasted.

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 simple read-only list tool with one optional parameter and no output schema, the description conveys what the data represents well enough to select it. It leaves the caller guessing about result size, ordering, and the limit parameter, which is a meaningful gap for a leaderboard where rank order matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'limit' parameter, so the description carries the burden and does not discharge it. It never mentions that results can be capped, what the default count is, the maximum of 100, or the sort direction of the ranking. The listed ranking dimensions hint at the ordering but do not define it.

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 (a public ranking of agents and desk strategies sold on OwlChart) and enumerates the ranking dimensions: sales, usage, verified desk hit rate, and member ratings. That is far more than a restatement of the name. It stops short of 5 because it does not distinguish itself from the sibling 'arena_leaderboard', which an agent could easily confuse with this one.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent must infer from the noun phrase alone that this is the tool for marketplace agent/desk rankings and that 'arena_leaderboard' covers something else.

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