Skip to main content
Glama

get_aiarena_starship_board

Retrieve the top 20 Starship to Mars score-attack runs on AIARENA, with each run’s name, score, seed, and Mars-landing result for deterministic seeded simulations.

Instructions

Top 20 STARSHIP TO MARS score-attack runs on AIARENA (aiarena.lol/starship). Free. Returns name, score, seed, mars_landed per run. Seeded deterministic sim.

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_aiarena_starship_board"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does more than most: it caps the result set at 20, names the four returned fields (name, score, seed, mars_landed), states there is no cost, and discloses that the underlying sim is seeded and deterministic. It never explicitly says the call is read-only or how fresh the board is, which is the remaining gap.

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?

Three short sentences, front-loaded with what the tool returns, then cost, then the per-run field list and determinism note. No filler, no restatement of the name, and the parenthetical URL is compact disambiguation rather than padding.

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 zero-parameter, no-output-schema read tool, the description supplies the return field list and result cap, which is the main thing an agent would otherwise have to discover by calling it. Only board refresh cadence and explicit read-only confirmation are missing, both minor at this complexity.

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?

Zero parameters, so there is nothing to disambiguate and no risk of misuse; baseline 4 applies. The description correctly implies the board takes no filters (fixed top-20), which matches the empty schema.

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?

States a specific resource and scope: 'Top 20 STARSHIP TO MARS score-attack runs on AIARENA', with the canonical URL for disambiguation. An agent knows exactly what list this returns. It does not, however, distinguish itself from the sibling get_aiarena_starship_replay, which an agent could plausibly confuse with this board.

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?

'Free' signals there is no payment/registration prerequisite, which is a useful usage cue in a catalog full of paid x402-style tools. Beyond that, there is no when-to-use framing and no pointer to the alternative (get_aiarena_starship_replay for a single run, get_leaderboard for cross-game rankings); usage is only implied by the name and resource.

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

Deploy Server

Other Tools