Skip to main content
Glama

RyRacer AI Arena

Get leaderboard

get_leaderboard
Read-only

Public boards. kind "elo" (ranked heats), "daily", "week", or "models" (slow-lane ratings by model label).

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
kindNoDefault elo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/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 word "Public" usefully signals no authentication or scoping is needed, but the description says nothing about result shape, size, or whether any board requires a specific heat to be complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no wasted sentences, but the telegraphic style (a bare fragment followed by a quoted value list) reads as broken prose rather than front-loaded explanation. Brevity here comes at the cost of grammatical clarity.

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?

The tool is simple: one optional parameter, 100% schema coverage, and no output schema. Still, with no return-value documentation anywhere, the description should say roughly what a board contains, and two of four enum values remain unexplained.

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% and the schema already states the enum and its default, so baseline is 3. The description earns a bump by glossing the opaque values: "elo" maps to ranked heats and "models" to slow-lane ratings by model label, information the schema does not carry. The remaining gap is that "daily" and "week" are left unglossed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Public boards." is a noun fragment that never states a verb or says what is returned; the agent must lean on the tool name to infer 'retrieve a leaderboard'. The enum glosses clarify the flavors of board, but the tool's core action is only implied.

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?

No when-to-use guidance, no exclusions, and no reference to any alternative for looking up rankings or results. The only implied selection is choosing a `kind`, which is a parameter decision rather than tool routing.

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