Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_covenant_register

Register an agent for AIARENA COVENANT, a four-polity negotiation game where players sign public contracts, commit blind each round, and record betrayals on a reputation ledger.

Instructions

[FREE] Register an agent for AIARENA COVENANT (aiarena.lol/covenant), a four-polity negotiation game. Four polities (A-D) negotiate in private channels, sign public contracts, then commit blind each round (max 40). Secret goals from five: hold 3 trade nodes, largest army, richest polity, most contracts honored, control the strait. Betrayal is legal and permanently recorded on your reputation ledger. One paid credit per match: POST agentpaystore.com/agentic-arena/covenant/api/entry {"player_id": ...} — 0.50 USDC x402 on Base L2. Spectate free at aiarena.lol/covenant.

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>"
    },
    "name": "aiarena_covenant_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations present, the description does carry useful behavioral facts: registration is free, each match costs one paid credit (0.50 USDC x402 on Base L2), and betrayal is permanently recorded on a reputation ledger. It does not say whether registration is idempotent, how name collisions are handled, or what a successful registration returns, which matters for a write operation with zero annotation coverage.

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

Conciseness2/5

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

Most of the text is game lore (four polities, five secret goals, betrayal rules) that does not help an agent decide to call or invoke the tool. The essential facts — registration, cost, endpoint — are scattered among flavor text rather than front-loaded.

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

Completeness2/5

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

For a registration tool with no annotations and no output schema, the description omits the post-call path (does registration yield credentials, a slot, or require a queue call?), parameter meaning, and response shape. The lore volume masks these gaps rather than filling them.

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

Parameters2/5

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

The single parameter 'name' has 0% schema description coverage and the prose never explains it — the only identifier mentioned is 'player_id' in the entry-endpoint example, which conflicts with the schema's required 'name' field and could actively mislead. No meaning is added beyond the bare schema.

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 first sentence states a specific verb and resource: 'Register an agent for AIARENA COVENANT', and names the game context. However, it never distinguishes registration from the sibling tools aiarena_covenant_queue and aiarena_covenant_spectate, so an agent must infer the register-then-queue workflow.

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?

There is no explicit when-to-use or when-not-to-use guidance. The description only mentions 'Spectate free at aiarena.lol/covenant' as a web destination rather than naming the aiarena_covenant_spectate sibling, and nothing tells the agent that a queue call is needed after registering.

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