Skip to main content
Glama

tokmeter_leaderboard

Read-only

Rank AI models or providers by cost, cost efficiency, tokens, cache hit rate, reasoning share, output volume, or records to compare spend and value within a chosen time scope.

Instructions

Rank the top N models or providers (default 10) in a scope by one metric: total cost, cost per 1M tokens (cost_efficiency), total tokens, cache hit rate (cache_rate), reasoning share (reasoning_rate), output tokens, or record count. Returns the entries in rank order with their metrics. Use it to answer "which model costs most / gives the best value"; for every metric of every model at once, use tokmeter_models.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTop N to show (default: 10)
scopeNoTime scope: today, week (last 7d), month (calendar month), or all (default)
entityNoRank models or providers (default: models)
projectNoFilter by project name/path substring
rank_byNoRanking metric (default: cost)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.19.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results come back in rank order with their metrics and that limit defaults to 10, which is useful behavioral context; it does not cover empty-result or tie-handling behavior, so not a 5.

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?

The purpose and default are front-loaded in the first sentence, and the sibling routing is placed last where it belongs. The mid-sentence enumeration of seven metrics is dense but every item earns its place since the schema enums alone would not convey them.

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 5 optional params, no output schema, and annotations covering read-only semantics, the description supplies what is missing: return ordering, default limit, and metric interpretation. It does not explain how project filtering interacts with entity ranking, a minor gap.

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 would be 3, but the description translates enum values into human meaning the schema does not: cost_efficiency = cost per 1M tokens, cache_rate = cache hit rate, reasoning_rate = reasoning share, output_volume = output tokens, records = record count. That is genuine added value beyond the schema.

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 (rank) and resource (top N models or providers) with the exact set of metrics available and the default N=10. It also names the sibling tokmeter_models and the condition that distinguishes it, so an agent can pick between the two without opening either schema.

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?

Gives an explicit use case ("which model costs most / gives the best value") and names the alternative tool plus the condition that selects it ("for every metric of every model at once, use tokmeter_models"). Nothing is left to inference.

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