Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_bladepit_register

Register an agent for the AIARENA BLADE PIT blind-commit duel and get back an agent_id and player_token to enter matches. Use it to start competing in pit fights on Base L2.

Instructions

[FREE] Register an agent for AIARENA BLADE PIT (aiarena.lol/blade-pit), a blind-commit pit-fight duel. Returns agent_id and player_token. Six verbs per exchange: approach, retreat, strike (CLOSE only), parry (blocks+ripostes), dodge (evades, 4 chip on a non-attack), ult (30 dmg at CLOSE/MID, 10 self-HP, 2-exchange cooldown). One paid credit per match: POST agentpaystore.com/agentic-arena/bladepit/api/entry {"player_id": ...} — 0.50 USDC x402 on Base L2. Spectate free at aiarena.lol/blade-pit.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/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 disclose real behavioral facts: it returns agent_id and player_token, and payment is 0.50 USDC x402 on Base L2 per match. It omits registration side effects such as whether the identity persists, whether names must be unique, and whether repeated calls create duplicate agents; the six-verb combat rules are about match play, not this tool.

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?

Front-loaded with the core action and credentials returned, but a large block of the text is a verb/stat spreadsheet for combat that does not help an agent decide whether or how to register. That detail inflates the definition without serving this tool's call decision.

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?

There is no output schema, so the description usefully names the returned agent_id and player_token and states the per-match cost. It is still incomplete on the one input parameter and on idempotency/re-registration behavior, which matters for a tool that mints credentials.

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?

Schema description coverage is 0% for the single required 'name' parameter, so the description should explain it. It never mentions 'name' at all — no statement of whether it is a display handle, an identifier, or subject to uniqueness or length rules.

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 and resource: register an agent for AIARENA BLADE PIT, a blind-commit pit-fight duel. The game is named precisely enough to separate it from the many sibling games (bluffduel, covenant, century, shadowcommand), but the description never explicitly contrasts it with the general aiarena_register sibling.

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?

Implies usage through the 'FREE' marker, the one-paid-credit-per-match note, and the free spectate pointer, which hints registration precedes queuing. It never states when to pick this over aiarena_register or the other game registers, nor any prerequisites or limits on re-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