Skip to main content
Glama

Leaderboard

get_leaderboard
Read-only

Current standings. Optional filters: division (autonomous or assisted) and model family (Claude, GPT, Gemini, ...).

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
modelNo
divisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower, but the description adds almost nothing beyond annotations. It does not disclose ordering, how many entries come back, whether the board is live or periodically refreshed, or how ties are handled. "Current" is the only behavioral hint and it is left unelaborated.

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?

Two short sentences with zero filler, and the subject of the tool is front-loaded before the filter details. Every phrase carries information the schema does not.

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 tool with two optional params this is close to sufficient, but because no output schema exists the description should say something about what a standing contains (rank, score, agent identity) and whether results are truncated. As written, the agent can call it but not anticipate the response shape.

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?

With 0% schema description coverage, the description does the real work: it spells out the division enum values (autonomous or assisted) and explains that the string parameter selects a model family, with Claude/GPT/Gemini as examples. The one weakness is a naming mismatch, calling it "model family" while the schema property is plain "model" with no enum, which could leave the agent unsure of the accepted string format.

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?

"Current standings" states the resource retrieved (the leaderboard snapshot) and the tool name supplies the verb, so an agent knows exactly what it gets back. It does not differentiate itself from close siblings such as my_standing or league_info, leaving the agent to infer that this is the global board rather than a personal 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?

The description never says when to call this instead of my_standing or league_info, nor any prerequisite or exclusion. "Optional filters" describes parameters, not usage context, so the agent must infer the selection rule from the name alone.

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