Skip to main content
Glama

arena_results

Read-only

FREE: scored or in-progress Arena round results — CoinGecko closing prices used for scoring, every prediction with abs % error, leaderboard with house:true/eligible flags and ineligibleReason (including 'not prize-eligible: no /v1/pulse call' through 2026-11-22 and 'not prize-eligible: no paid call' from 2026-11-23), prize-eligible winner, and payout status with Solscan tx links when paid.

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

Input Schema

NameRequiredDescriptionDefault
roundIdNoRound id YYYY-MM-DD (defaults to current entry round)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds substantial context beyond them: CoinGecko closing prices as the scoring source, absolute-percentage error per prediction, house/eligibility flags, dated ineligibleReason strings, and Solscan transaction links for paid payouts. It stops short of disclosing response size, pagination, or behavior when a round has no entries yet.

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?

It is a single dense sentence, but it is front-loaded with the essential fact (free, round results) and every subsequent clause describes real payload content rather than filler. The nested parentheticals, especially the two dated ineligibleReason strings, make it harder to scan than it needs to be.

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?

With no output schema, the description carries the full burden of explaining return values and does so in detail — prediction errors, leaderboard flags, winner, payout status with transaction links. What is missing is operational detail: pagination, result-set size, and how an unscored or empty round is represented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single roundId parameter is fully documented in the schema itself, including the YYYY-MM-DD format and the default-to-current-round behavior. The description contributes only the implicit notion that a round can be in progress or scored; it never mentions roundId or its default directly, so baseline 3 applies.

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 opening clause 'scored or in-progress Arena round results' names a specific resource and states its scope (free, per-round), and the enumeration of contents (predictions with abs % error, leaderboard flags, payout status) makes the payload unambiguous. It does not explicitly contrast itself with arena_current_round or arena_history, which cover adjacent round data, so it falls short of full sibling differentiation.

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 'FREE:' prefix signals cost but not when to choose this over the many sibling arena tools. There is no statement of when-not to use it, no mention that arena_current_round or arena_history exist as alternatives, and no prerequisites or rate-limit context.

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