Skip to main content
Glama
Sea of Fox RTS MCP

Sea of Fox RTS MCP

by DRMAPLEE

rts_build_sites

Read-only

Find server-validated building coordinates on the current island, including shoreline sites for docks. Choose valid build sites before placing; candidates can expire as the match changes.

Instructions

Find server-validated candidate coordinates for a building on the land builder’s current island. Candidates can become invalid as the match changes. For docks the game searches the shoreline.

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": {
      "builderId": "<builderId>",
      "kind": "<kind>"
    },
    "name": "rts_build_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nearNo
builderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/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 genuine behavioral context beyond that: results are server-validated, they can go stale as the match changes, and dock searches are performed along the shoreline by the game. It does not cover rate limits or what happens for an unknown builderId.

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 with the core purpose front-loaded and no filler. The staleness note is slightly awkwardly phrased ('as the match changes') but each sentence carries information.

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 a read-only lookup with no output schema, the description should at minimum indicate what comes back and what the caller supplies; it conveys 'candidate coordinates' but leaves the return shape (list? ranked?) and the meaning of 'kind'/'near' ambiguous. Adequate to attempt the call, not adequate to call it confidently on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, including a nested 'near' object, so the description must carry the meaning and largely does not. It implies builderId ('land builder') and kind ('building' vs 'docks'), but never explains the allowed 'kind' string values (no enum exists), what 'near' does, or the coordinate bounds encoded in the schema.

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 resource: 'Find server-validated candidate coordinates for a building,' scoped to 'the land builder's current island' and with a special case for docks. The purpose is unmistakable and distinct from the observe/order/wait siblings, though it doesn't explicitly name a sibling it competes with.

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?

Usage is only implied: an agent can infer this is the lookup step before placing a building, and the note that 'candidates can become invalid as the match changes' hints at re-invocation timing. There is no explicit when-to-use/when-not-to-use guidance or stated prerequisite (e.g., that a valid builderId must exist).

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