Skip to main content
Glama

Ezkielyna Public Tools

Weekly usage leaderboard

usage_leaderboard
Read-onlyIdempotent

Most-used AI models on Ezkielyna over the last 7 days (requests, share %, tokens, distinct users) and the change versus the week before. Only models used by at least 3 people are ranked. Users are mostly Indonesian developers with coding agents, so this is one gateway's sample, not national market share. Data CC BY 4.0. Free, no API 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": "usage_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many models to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses result-shaping behavior: only models with at least 3 distinct users are ranked, so the list is deliberately incomplete. It also flags the sampling caveat ('one gateway's sample, not national market share'), the licensee/attribution terms (CC BY 4.0), and that no API key is needed. This is real added context, short only of stating sort order or data freshness.

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 core answer (what it returns and over what period), then caveats, then licensing/access. Four sentences with little waste, though the CC BY 4.0 and 'free, no API key' lines lean toward boilerplate rather than invocation guidance.

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 description correctly compensates by enumerating returned fields and the comparison baseline (prior week). The eligibility threshold and sampling caveat round out interpretation. Minor omissions — sort order and how recent the 7-day window is — keep it short of complete.

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?

There is a single optional parameter (`top`, max 20) already fully documented in the schema at 100% coverage, so the schema does the work. The description adds no meaning about how `top` interacts with the ranking or what happens when fewer eligible models exist, which is the baseline-3 case.

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 (most-used AI models) with a fixed time scope (last 7 days) and enumerates the metrics returned (requests, share %, tokens, distinct users, week-over-week change). That is enough to separate it from siblings such as compare_models or lowest_price_models, though it never names an alternative 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?

Usage is only implied — an agent can infer 'use this to see the usage ranking' but there is no explicit when-to-use statement, no stated exclusions, and no pointer to a sibling for related questions like model comparison or pricing. The fixed 7-day window is stated, which implicitly rules out custom date ranges, but that is the only guidance present.

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