Skip to main content
Glama
Sea of Fox RTS MCP

Sea of Fox RTS MCP

by DRMAPLEE

rts_observe

Read-only

Read current RTS match state—overview, units, buildings, islands, reserves, and buffered events—with filters and pagination to find IDs and positions.

Instructions

Read the current match, controlling peer, treasury, economy, units, visible contacts, or terrain landmarks. Use overview first; use paginated units/buildings/islands/reserves for IDs and positions. Events are buffered briefly.

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

Input Schema

NameRequiredDescriptionDefault
idNoExact record ID, or event source/target ID
kindNoUnit/building kind or event type
viewNooverview
limitNo
cursorNoUse nextCursor returned by a paginated view
filterNoScope for units/buildings/islands. Other means outside your faction, not necessarily hostile. Use all for reserves.
islandIdNo
afterTickNoFor events, only return events after this tick

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuine behavioral fact not in the annotations: 'Events are buffered briefly,' warning that event data is transient and may be lost. It does not quantify the buffer window or explain paging behavior in prose, which keeps it at 4.

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 short sentences, front-loaded with the resource list and then the operational guidance. Every sentence carries content. The first sentence is a long enumeration that could be tightened, but no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter, no-output-schema read tool with 63% schema coverage, the description covers the view-selection story and the transient-event caveat. It leaves gaps on how pagination limits behave, what 'kind' and 'id' filter relative to, and what overview returns versus paginated views. Adequate but not complete.

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 description coverage is 63%, with several parameters (limit, islandId, afterTick covered) documented inline and enums for view and filter. The description adds the notion that views are paginated and that IDs/positions come from them, but it says nothing about limit, cursor, kind, or the own/faction/other/all filter scope. Since the schema already carries the heavier documentation, this sits at the baseline of 3.

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?

The description opens with a specific verb ('Read') and enumerates the resources available (match, peer, treasury, economy, units, contacts, terrain). The second sentence maps those resources onto the named views, so an agent can distinguish 'overview' from 'units/buildings/islands/reserves' and 'events'. It does not explicitly differentiate itself from siblings like rts_order or rts_wait, which keeps it below a 5.

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 gives concrete routing advice: 'Use overview first' and 'use paginated units/buildings/islands/reserves for IDs and positions.' That tells the agent which view to pick for which need. It stops short of naming alternatives outside this tool or stating when not to use it.

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