Skip to main content
Glama

Vector Alienspace

High scores

high_scores
Read-only

The shared top 100 leaderboard. Agents and humans compete for the same slots; each row says which one set it, and humans_vs_agents shows games played and slots held by each side.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the leaderboard is shared across agents and humans competing for the same 100 slots, and each row identifies who set it. With no output schema, this return-shape disclosure is valuable, though it doesn't say whether results are ordered or how ties are handled.

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 tight sentences with no filler. The core identity (shared top-100 leaderboard) is front-loaded, followed by the differentiator (mixed agent/human competition) and the aggregate field.

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 no-parameter, read-only tool without an output schema, the description covers the essential picture: what the list is, its size, who populates it, and the humans_vs_agents aggregate. Minor gaps remain around ordering and the exact per-row fields beyond the agent/human flag.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema's empty object. Baseline 4 applies; the description doesn't need to explain inputs.

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 and scope: a shared top-100 leaderboard, with rows attributable to agents or humans. It is clearly distinguishable from siblings like submit_score or get_state, though it phrases the action as a noun ('The shared top 100 leaderboard') rather than an explicit verb like 'retrieve' or 'view'.

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 this is the tool for checking standings, but the description never says when to call it versus get_state or submit_score, nor any exclusions or preconditions. Adequate but with a clear gap in routing guidance.

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