Skip to main content
Glama
Sea of Fox RTS MCP

Sea of Fox RTS MCP

by DRMAPLEE

rts_wait

Read-only

Waits for a game condition—such as tick, phase, unit status, building, voyage arrival, or event—for up to 20 seconds, then returns a fresh overview; timeouts return matched=false.

Instructions

Wait for an observed condition for up to 20 seconds, then return a fresh overview. Timeout is a normal result with matched=false. For a voyage the wait matches arrival or a blocked route; inspect the ship detail before landing. For landing use type=unit, status=ashore and the islandId.

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": {
      "until": "<until>"
    },
    "name": "rts_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
untilYes
afterTickNoRequire state newer than this tick. Use the receipt tick after issuing an order to avoid matching stale state.
timeoutMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, and the description adds what matters beyond that: a 20s cap, a fresh overview returned even on timeout, and matched=false as a normal terminal result. This is valuable return-shape context given there is no output schema.

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 tight sentences, front-loaded with the core behavior and the timeout caveat before the per-type recipes. No filler, though the 'inspect the ship detail before landing' clause is slightly oblique.

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?

For a blocking wait tool with no output schema and a seven-variant oneOf, the definition covers the essentials an agent needs: duration cap, timeout semantics, and the two most error-prone selector patterns. Only the less common selector types go unelaborated.

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 only 33%, and the description compensates for just part of it: it explains voyage matching semantics and the unit/status/islandId landing combination. The tick, control, phase, building, and event variants remain structurally defined but semantically unexplained, and timeoutMs is only echoed as 'up to 20 seconds'.

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 effect: wait on an observed condition up to 20 seconds, then return a fresh overview. That is clearly distinct from rts_observe (snapshot) and rts_order (mutation), though siblings are not named explicitly.

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?

Conveys the core usage context (block until a condition holds, timeout is a normal outcome) and gives a concrete landing recipe, but never says when to prefer rts_observe or rts_order instead, nor when not to wait at all.

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