Skip to main content
Glama

LLMBenchmark.ai MCP Server: LLM Benchmarks and API Prices

get_leaderboard

The top models on one category's board. category is one of overall, coding, agentic, reasoning, math, knowledge, design (see list_categories). limit is 1 to 50. overall is the LLMBenchmark Index: a weighted mean of the Vibe Coding Index, the agentic, reasoning, math and knowledge indexes, the Artificial Analysis Intelligence Index and the LMArena text Elo, with a 90% margin.

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
categoryNooverall

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden of explaining behavior and does so reasonably well: it states that results are scoped to one category, that limit is bounded between 1 and 50, and it explains the composition of the default 'overall' index including its 90% margin. It does not explicitly state read-only behavior or output ordering, but 'top models' strongly implies a ranked retrieval.

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 description is compact and front-loads the core purpose before documenting category values and limit. The long definition of the 'overall' index is justified because it is the default category, though the first sentence could be made more action-oriented with an explicit verb.

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?

For a simple two-parameter read tool with an output schema, this is largely complete: it covers category semantics, valid limit range, and the meaning of the default overall index. Remaining gaps such as explicit defaults and exact ordering are minor and partially covered by schema defaults or implied by 'top models'.

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 description coverage is 0%, so the description must compensate, and it largely does: it enumerates all seven allowed category values, points to list_categories, and gives the valid limit range of 1 to 50. It does not restate the default limit of 10 or default category of overall, but those are visible in the schema defaults.

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 identifies the resource and scope: top models on a leaderboard for one category. It is clearly distinguishable from list_categories by referencing it for category values, though it does not explicitly distinguish itself from other retrieval siblings such as get_model or compare_models.

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 mostly implied by the phrase 'top models on one category's board'. The description points to list_categories for valid category values, which is useful, but it gives no explicit when-to-use or when-not-to-use guidance versus alternatives like compare_models or recommend_model.

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.