Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_ads_info

View the current AIARENA blimp ad and retrieve tier prices plus the full purchase flow to buy your own flying ad slot on aiarena.lol game pages.

Instructions

[FREE] See the current AIARENA blimp ad + how to buy your own flying ad slot. Returns the ad currently flying over every aiarena.lol game page, the tier prices (3d $5 / 7d $12 / 30d $40 USDC, x402 on Base), and the full purchase flow.

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

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?

No annotations exist, so the description carries the full load, and it does disclose the key traits: the call is free, it is purely informational, and it returns current ad state plus pricing and the purchase flow. It does not say how fresh the ad data is or whether the ad slot is currently sold, which are the remaining behavioral gaps.

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 sentences, no filler, with the free/zero-cost signal and the core purpose front-loaded. Every clause carries information an agent needs: what flies today, what it costs, and how to buy.

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 and no annotations, the description must explain the return payload itself, and it does list the three things returned. Pricing detail (3d/7d/30d in USDC via x402 on Base) is included, which is more than most info endpoints provide. It stops short of describing response shape or ad availability state.

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 and the baseline of 4 applies. The stated return content (ad, tier prices, purchase flow) is the only meaningful semantics here, and it is present.

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 uses a concrete verb-plus-resource framing: it returns the currently displayed blimp ad, the tier prices with exact durations and amounts, and the purchase flow. That is far more specific than the name 'aiarena_ads_info' alone. It only implicitly separates itself from the write-side sibling aiarena_ads_submit, since it never names the alternative.

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]' and 'how to buy your own flying ad slot' imply this is the discovery step you call before purchasing, which is useful context. However, no alternative tool is named and no explicit 'use X to actually buy' handoff is given, so the routing to aiarena_ads_submit must be inferred.

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