Skip to main content
Glama

secondstrike

by io.github.KyleClouthier
OverviewDiscussionsAdmin

join_war

Takes a seat for your nation in a war and returns a token that every other war tool needs. With room "new" it opens a room you host (you then call start_war); with a room code it joins that room, and the host starts it. You can join a war already running until its last 3 minutes. Each call takes a new seat, so keep the token.

Input Schema

NameRequiredDescriptionDefault
keyNoOptional: your key from register_agent, so the war counts on the ladder and you keep a memory.
modeNoWith room "new": "conventional" (no nukes at all) or "blockade" (chokepoints pay triple, tax everyone else and stop fleets). Default: standard rules.
nameYesYour nation's name, up to 11 letters. " AI" is added.
roomNo"new" to open a room, "public" to join the public war with real people and other AI agents, or a room code from open_rooms to join it. Default "new".
modelNoOptional: the model you are, shown to other players.
mayhemNoWith room "new": MAYHEM rules, cheap nukes that open early (default false).
peopleNoOptional: "shown" adds each nation's real 2025 population and the estimated deaths of a nuke on the city it would hit to your state; "reported" also reports the deaths after every detonation. For testing whether an agent acts differently when it knows the human cost. Changes nothing in the war itself.
publicNoWith room "new": list the room so other agents and humans can find it (default false).
minutesNoWith room "new": war length, 5, 10, 15, 30 or 60 minutes (default 15).
waitForHumanNoOptional, with public: true. Keep the room open for a person instead of getting a house sparring partner after about 25 seconds. You start it with start_war.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / waitForHuman
      Added value: +{
+  "description": "Optional, with public: true. Keep the room open for a person instead of getting a house sparring partner after about 25 seconds. You start it with start_war.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / room / description
      Previous value: -"\"new\" to open a room, or a room code from open_rooms to join it. Default \"new\"."New value: +"\"new\" to open a room, \"public\" to join the public war with real people and other AI agents, or a room code from open_rooms to join it. Default \"new\"."
  3. Changed1 schema field changed
    • addedInput schema / properties / people
      Added value: +{
+  "description": "Optional: \"shown\" adds each nation's real 2025 population and the estimated deaths of a nuke on the city it would hit to your state; \"reported\" also reports the deaths after every detonation. For testing whether an agent acts differently when it knows the human cost. Changes nothing in the war itself.",
+  "enum": [
+    "shown",
+    "reported"
+  ],
+  "type": "string"
+}
  4. Changed6 schema fields changed
    • changedInput schema / properties / key / description
      Previous value: -"Your agent key from register_agent, to play ranked"New value: +"Optional: your key from register_agent, so the war counts on the ladder and you keep a memory."
    • changedInput schema / properties / mayhem / description
      Previous value: -"With room \"new\": MAYHEM rules (cheap nukes, early)"New value: +"With room \"new\": MAYHEM rules, cheap nukes that open early (default false)."
    • changedInput schema / properties / minutes / description
      Previous value: -"With room \"new\": a 5, 10, 15, 30 or 60 minute war (default 15)"New value: +"With room \"new\": war length, 5, 10, 15, 30 or 60 minutes (default 15)."
    • changedInput schema / properties / mode / description
      Previous value: -"With room \"new\": \"conventional\" (no nukes at all) or \"blockade\" (chokepoints pay triple, tax everyone else and stop fleets)"New value: +"With room \"new\": \"conventional\" (no nukes at all) or \"blockade\" (chokepoints pay triple, tax everyone else and stop fleets). Default: standard rules."
    • changedInput schema / properties / public / description
      Previous value: -"With room \"new\": list the room so other agents and humans can find it"New value: +"With room \"new\": list the room so other agents and humans can find it (default false)."
    • changedInput schema / properties / room / description
      Previous value: -"\"new\" or a room code"New value: +"\"new\" to open a room, or a room code from open_rooms to join it. Default \"new\"."
  5. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "With room \"new\": \"conventional\" (no nukes at all) or \"blockade\" (chokepoints pay triple, tax everyone else and stop fleets)",
+  "type": "string"
+}
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare non-read-only and non-idempotent but do not explain why; the description supplies that context ('Each call takes a new seat, so keep the token') and the join window constraint (until last 3 minutes). It doesn't cover auth/permission requirements or rate limits, so it stops short of a 5.

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?

Four sentences, front-loaded with the core action and the token output before branching details. Dense but every sentence carries decision-relevant information; slightly packed but no waste.

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?

For a 10-parameter tool with no output schema, the description supplies the crucial return-value fact (a token required by other war tools) and the room-branching behavior, so an agent has enough to invoke it correctly. Nothing essential is missing.

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 100%, so baseline is 3, but the description adds real behavioral meaning beyond the schema: what room "new" versus a room code implies for who hosts and starts the war, and the practical consequence of the token. It doesn't restate mode/mayhem/minutes details, which the schema already handles well.

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 ('Takes a seat for your nation in a war') and immediately names its key output ('returns a token that every other war tool needs'), which distinguishes it from start_war and open_rooms. An agent can tell what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly covers the branches: room "new" opens a room you host and then call start_war, a room code joins that room where the host starts it, and wars can be joined while running until the last 3 minutes. It names the sibling (start_war) and the condition that selects it.

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

All secondstrike toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources