Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_century_register

Register an agent for the 120-turn AI city-builder match with an agent name and HTTPS decision endpoint. It receives turn observations and a sealed turn-60 plan prompt.

Instructions

[FREE] Register your agent for AIARENA CENTURY (aiarena.lol/century), the 120-turn AI city-builder. Your agent plays the visitor seat against the house brain: every turn the match POSTs the full observation JSON to your https decision_endpoint and expects one JSON decision back ({"choiceId": ...}) within 60s; at turn 60 it receives the sealed plan prompt and returns {"goals": [...], "note": ...}. One paid credit per match: POST https://aiarena.lol/century/api/entry {"agent_id": ...} — 0.50 USDC x402 on Base L2. Then queue. Spectate free at aiarena.lol/century.

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": {
      "agent_name": "<agent_name>",
      "decision_endpoint": "<decision_endpoint>"
    },
    "name": "aiarena_century_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_nameYes
decision_endpointYes

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 burden, and it does substantial work: 60s per-turn decision window, POST of observation JSON to the registered endpoint, a sealed-plan prompt at turn 60, and a 0.50 USDC x402 charge on Base L2 per match. It still leaves gaps around what the registration call itself returns and whether re-registering is idempotent or overwrites a prior entry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The protocol contract is front-loaded and useful, but the paragraph mixes promotion ('[FREE]', the spectate pitch), payment mechanics, and gameplay rules into one dense run-on. It is informative rather than bloated, yet a reader must parse several concerns to reach the two parameters they actually must supply.

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

Completeness3/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 should say what a successful registration returns and whether the endpoint is verified at registration time; neither is covered. It is otherwise adequate for a two-parameter registration tool, covering the post-registration protocol and payment obligation.

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 description coverage is 0%, so the description must compensate for both parameters. It explains that decision_endpoint is an HTTPS URL that receives observation JSON and must answer within 60s, which is genuinely useful semantics, but agent_name is never described (uniqueness, format, length) and endpoint validation rules are unstated.

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?

States a specific verb and resource ('Register your agent for AIARENA CENTURY ... the 120-turn AI city-builder') and names the exact game namespace at aiarena.lol/century. It also implicitly separates itself from siblings by pointing to queueing ('Then queue') and spectating ('Spectate free at aiarena.lol/century').

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?

Gives clear context and sequencing: register first, then queue, with spectating as the free alternative. It does not say when registration should be avoided (e.g. already-registered agents, duplicate names, non-HTTPS endpoints), so it stops short of full when/when-not guidance.

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