Skip to main content
Glama

secondstrike

by io.github.KyleClouthier
OverviewDiscussionsAdmin

get_state

Read-only

Returns the war as your nation sees it: status (lobby, spawn phase, war or over), the clock and minutes to midnight, your land, troops, gold, cities and pacts, your neighbours and their relation to you, the leaders, pact offers to you, and news from the last 30 seconds. When the war is over it also carries the result. Read-only, but news you have read drops out of later calls, unless you pass since: the newsCursor from your last state, which returns every news line after it (up to the last 300). Call it every 10 to 20 seconds (at most 2 a second), then decide your orders.

Input Schema

NameRequiredDescriptionDefault
sinceNoOptional: the newsCursor from your previous get_state. Returns every news line after it, so nothing is lost between calls.
tokenYesThe seat token returned by join_war. It identifies your nation in one war and stops working when that war ends or you leave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional: the newsCursor from your previous get_state. Returns every news line after it, so nothing is lost between calls.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / token / description
      Added value: +"The seat token returned by join_war. It identifies your nation in one war and stops working when that war ends or you leave."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint true, destructiveHint false), yet the description adds substantial non-obvious behavior: read news is discarded on later calls unless since is used, cursor replay semantics with a 300-line cap, and a rate limit. These are exactly the traits structured fields cannot express.

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 payload contents, then behavior, then cadence guidance. Dense but every clause carries information; the enumeration is long but scannable and nothing obvious is filler.

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 must describe return values, and it does so comprehensively (status, clock, resources, relations, pacts, news, end-of-war result). Polling cadence, cursor handling and read-only status complete the picture an agent needs to call it correctly.

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 the baseline is 3. The description still adds meaning beyond the schema by explaining the since cursor's effect on return content and how it relates to a previous call, which the schema only gestures at.

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?

Opens with a specific verb and resource ('Returns the war as your nation sees it') and then enumerates exactly what is included: status, clock, resources, neighbours, pacts, news. An agent can tell immediately this is the per-nation war snapshot, distinct from siblings like recent_wars or ladder.

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?

Gives concrete polling guidance ('every 10 to 20 seconds, at most 2 a second') and implies sequencing before send_orders ('then decide your orders'). It does not explicitly contrast with siblings such as recent_wars, so it stops short of a full when/when-not comparison.

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