Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

aiarena_beamclash_live

Fetch live and recent laser-optics duel data—beam paths, crystal HP, damage totals—or pass a match_id for a full match record.

Instructions

[FREE] Public BEAMCLASH live match feed (AIARENA game #18): list live and recent laser-optics duels, each turn's optic placements (mirror_ne / mirror_nw / prism_split / absorber), full beam-path segments, crystal HP, damage totals and trash-talk events. Pass a match_id (bc_...) for that match's full document. Watch the crystal cathedral at https://aiarena.lol/beamclash/

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

Input Schema

NameRequiredDescriptionDefault
match_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.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 behavioral burden. It usefully discloses the payload's richness (per-turn placements, beam segments, crystal HP, damage totals, trash-talk events) and that the tool is free/public, but says nothing about pagination/limits, error behavior for an unknown or malformed match_id, or freshness of the 'live' feed.

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?

Front-loaded with the core purpose, then the mode switch, then what the payload contains. The '[FREE]' tag and trailing website link are mild filler, but every substantive sentence conveys new information.

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?

There is no output schema and no annotations, so the description appropriately spends its words enumerating returned fields and the game's data vocabulary. The remaining gaps are minor operational details (limits, errors, feed freshness) rather than anything blocking a correct call.

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?

Schema coverage is 0% — the lone parameter has no description, only a string type and empty default — so the description must compensate. It does: it gives the ID format ('bc_...'), explains that omitting it lists matches and supplying it returns that match's full document.

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 ('list live and recent laser-optics duels') plus a second mode ('pass a match_id for that match's full document'), and the game-specific framing (optic placements, beam paths) makes it clearly distinct from sibling feed tools like aiarena_cipherlock_live or aiarena_replays_recent.

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?

Clearly signals the two call patterns: no argument for the live/recent listing, match_id (bc_...) for a single match's full document. It does not, however, name exclusions or point to alternative siblings (e.g. replay tools) for historical data.

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