Skip to main content
Glama
Sea of Fox RTS MCP

Sea of Fox RTS MCP

by DRMAPLEE

rts_order

Destructive

Submit up to 12 real-time strategy orders in sequence; the server validates each order, allows partial success, and uses a batch ID to recover uncertain acknowledgements.

Instructions

Apply up to 12 orders in sequence. The server validates control, ownership, placement, fog, resources and routes. Orders can partially succeed. Stop on the first rejection by default. Supply a fresh batchId and reuse it with exactly the same orders to recover an uncertain acknowledgement.

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": {
      "orders": "<orders>"
    },
    "name": "rts_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
ordersYes
batchIdNo
continueOnErrorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (destructive, open-world, non-read-only), the description discloses validation checks, partial batch success, stop-on-first-rejection behavior, and idempotent retry via batchId. It does not document the response shape or side effects per order type, but the schema carries detailed per-order descriptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core operation and followed by validation, partial-success, and retry behavior. Each sentence contributes distinct operational information with no redundant restatement.

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 complex, destructive batch tool with no output schema, the description covers sequencing, validation, partial success, and retry recovery well. It leaves response/result inspection and explicit tool-choice guidance unstated, which are minor gaps given the schema's per-order detail.

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 description coverage is reported as 0%, so description-side compensation matters. The description adds key semantics for batchId (fresh value plus reusing exactly the same orders for an uncertain acknowledgement) and for default failure handling (the behavior controlled by continueOnError), plus the 12-order cap. It does not enumerate order-type parameters, relying instead on the rich oneOf 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?

The description uses a specific verb and resource: 'Apply up to 12 orders in sequence,' with a hard cap and sequential semantics. It does not name sibling tools or explicitly distinguish this operation from observation/catalog tools, so the purpose is clear but not fully differentiated.

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?

It gives implicit usage context for issuing batches and recovering uncertain acknowledgements with a reused batchId, and it explains the default stop-on-rejection behavior. However, it does not explicitly say when to choose this tool over observing first or using other RTS tools, so guidance is implied rather than directive.

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