Skip to main content
Glama
warapp-mcp

warapp-mcp

by chrischall

Recent war.app push events

warapp_recent_events
Read-onlyIdempotent

List the war.app game-update pushes this server process has received (newest first): which game changed and when. Only games watched by warapp_wait_for_turn are listened to; a push says only that a game changed, so re-read it with…

Instructions

List the war.app game-update pushes this server process has received (newest first): which game changed and when. Only games watched by warapp_wait_for_turn are listened to; a push says only that a game changed, so re-read it with warapp_get_game. Also reports whether the push socket is connected and its transport (websocket or xhr-polling). Read-only.

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": "warapp_recent_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many events (default 20, max 100).
game_idNoOnly events for this game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description still adds substantive behavior: the buffer is process-local, entries are newest first, and the call also reports socket connection state and transport (websocket vs xhr-polling). It also warns that a push is a change signal, not game data. It omits retention/eviction behavior for the event buffer beyond the limit parameter.

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?

Three dense sentences, front-loaded with what the tool returns and followed by the precondition and the follow-up action; nothing is buried. The trailing "Read-only." is mildly redundant given readOnlyHint=true, which keeps it from a 5.

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?

With no output schema, the description carries the burden of explaining returns, and it does: game identity, timestamp ordering, plus socket status and transport. Combined with the listened-games precondition and the re-read guidance, an agent has everything needed to call it and interpret the result; only exact field names are unspecified, which is minor for a small list tool.

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 coverage is 100% and both parameters (limit, game_id) already carry descriptions, so the schema does the heavy lifting. The description adds only the framing that events identify which game changed, which helps interpret game_id but adds no format or edge-case detail. Baseline 3 is appropriate.

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-plus-resource ("List the war.app game-update pushes this server process has received"), states ordering (newest first), and says exactly what each entry contains (which game changed and when). The phrase "this server process" also scopes it away from a global event log, so it is distinguishable from siblings like warapp_get_game or warapp_wait_for_turn.

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 supplies a real usage precondition (only games watched by warapp_wait_for_turn are listened to) and routes the agent to the correct follow-up: "a push says only that a game changed, so re-read it with warapp_get_game." That is strong when-to-use and what-to-do-next guidance. It stops short of an explicit contrast such as when to poll this list versus calling warapp_wait_for_turn or warapp_get_live_board directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.