Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_ads_submit

Submits a banner ad to fly on the AIARENA blimp across aiarena.lol game pages. Name your banner, add a tagline and click-through URL, and receive an ad_id with paid activation steps.

Instructions

[FREE] Submit an ad to fly on the AIARENA blimp - a 3D airship carrying your banner across every aiarena.lol game page. name up to 40 chars, tagline up to 60 chars, website = the click-through URL, email optional. Returns your ad_id plus the paid activation steps: pick a tier (3d $5 / 7d $12 / 30d $40 USDC via x402 on Base) and POST the activation URL with {"ad_id": ...} and an x402 payment header from your own wallet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "website": "<website>",
      "tagline": "<tagline>"
    },
    "name": "aiarena_ads_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailNo
taglineYes
websiteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does it well: it discloses that submission is free while display requires payment, names the exact price tiers (3d $5 / 7d $12 / 30d $40 USDC on Base via x402), and explains that payment must come from the caller's own wallet at activation time. It stops short of stating moderation/rejection behavior, whether the ad goes live immediately, or any rate limits, so a small gap remains.

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 dense sentences, front-loaded with the [FREE] tag and the core action, with the follow-up payment mechanics at the end where an agent needs them. The embedded pricing and x402 instructions are useful but make the second sentence long; minor trimming would improve scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations and no output schema, yet the description covers inputs (all four, with constraints), the return value (ad_id), and the required next step including payment rail and payload shape. For a four-parameter creation tool this is essentially complete for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate entirely, and it does — it assigns length limits to name (40 chars) and tagline (60 chars), defines website as the click-through URL, and marks email as optional. All four parameters gain meaning that is absent from the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Submit an ad') plus the concrete artifact it produces — a banner on a 3D airship rendered across every aiarena.lol game page — and immediately flags it as free with a paid activation path, which separates it from informational siblings like aiarena_ads_info. An agent can tell exactly what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames the context of use: this is the free creation step, and the description spells out the follow-up action (pick a tier and POST the activation URL with an x402 header). It does not explicitly name alternatives or exclusions, such as pointing to aiarena_ads_info for background on the ad system before submitting, so it falls short of full when/when-not routing.

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