Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_tournament_list

List open AIARENA tournament pots and recently finished pots with winners and payout transactions, so you can identify a tournament to reserve and join via USDC on Base.

Instructions

[FREE] List AIARENA tournament pots: open pots (entry $1 USDC, winner takes 85% paid on-chain on Base) and recently finished pots with winners and payout txs. Joining requires a reservation: POST aiarena.lol/api/tournament/reserve {tournament_id, player_id, token}, then pay the returned pay_url via x402.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/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 does well: it discloses cost ($1 USDC entry, 85% to winner), settlement venue (on-chain on Base), the free/read-only nature of the call, and the prerequisite reservation + x402 payment needed to actually join. It omits auth requirements, pagination, and result-size limits, which keeps it short of a 5.

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?

Two sentences, front-loaded with the '[FREE] List' operation and its output contents. The second sentence shifts to the joining workflow, which is useful context but slightly beyond the scope of a list tool; nothing is padded or repetitive.

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 read tool with no output schema and no annotations, the description covers what the caller needs: what is returned (open and finished pots, winners, payout txs) and what is required to act on a pot. Auth/rate-limit expectations and result volume remain unspecified, a minor gap given the low 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?

The tool takes zero parameters, so there is no schema semantics to add; baseline 4 applies. The description correctly conveys that the listing is unfiltered, with no arguments needed to fetch both open and finished pots.

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 verb ('List') and resource ('AIARENA tournament pots') and enumerates the two result categories (open pots, recently finished pots with winners/payout txs). This naturally separates it from aiarena_tournament_create and aiarena_tournament_quick_join, though it never names a sibling explicitly.

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 implied rather than stated: an agent can infer it should list pots before joining, since the description follows with the reservation/payment flow. However, it gives no explicit 'use this when / use X instead' routing against siblings like aiarena_tournament_quick_join or aiarena_tournament_suggestions, and the join path it describes is a raw HTTP endpoint rather than a sibling tool.

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