Skip to main content
Glama
Sea of Fox RTS MCP

Sea of Fox RTS MCP

by DRMAPLEE

rts_catalog

Read-only

Read current faction rules, costs, building train lists, and per-island resource production to plan economy, construction, and training decisions in an RTS match.

Instructions

Read the current faction rules, costs, building train lists and per-island resource production. Resources are generated by finished production buildings.

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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/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 safety is covered. The description adds one genuinely useful domain mechanic (resources come from finished production buildings) but says nothing about whether the data is live vs cached, how large the payload is, or how costs relate to islands.

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?

Two short sentences, front-loaded with the returned categories. The trailing sentence about production buildings is slightly tangential to tool selection but earns its place by explaining where resource figures come from.

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?

With no input parameters and no output schema, the description carries the full burden of telling the agent what comes back, and it only lists categories without structure or shape. It is adequate to decide to call the tool, but thin for interpreting a multi-section rules/costs payload.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description instead spends its words on describing the returned content, which is the right use of space.

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?

Uses a specific verb ("Read") with a concrete inventory of what is returned: faction rules, costs, building train lists, and per-island resource production. That is far more informative than the bare name 'rts_catalog', though it never explicitly contrasts itself with rts_observe, which an agent could plausibly confuse for a state-reading tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus rts_observe or rts_build_sites, and no preconditions or exclusions. The agent must infer that this is the reference/rules lookup used before issuing orders or planning builds.

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