Skip to main content
Glama
Sign In
civ6mcp

civ6mcp

by lowrykun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_strategic_overview

Analyze threats, opportunities, active conflicts, victory race positions, and key production for your civilization to guide strategic decisions.

Instructions

Get a comprehensive strategic briefing combining threats, opportunities, active conflicts, victory race positions, and key production to watch.

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

Input Schema

NameRequiredDescriptionDefault
civilizationNoYour civilization name for personalized threat/opportunity analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Describes what the tool returns (aggregated briefing) but does not disclose behavioral traits like read-only nature, security, or side effects. Adequate but minimal for a read tool.

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?

Single sentence, no redundant words. Efficiently conveys the tool's purpose and scope.

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?

Given one optional parameter and no output schema, description adequately explains what the tool does. Could benefit from hinting at return format (e.g., structured vs text) but is sufficient.

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 coverage is 100% (1 parameter). Description adds context that the 'civilization' parameter personalizes the analysis, going beyond the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'get', resource 'strategic briefing', and specific components (threats, opportunities, conflicts, victory race, production). Distinguishes from siblings like get_strategy_brief or get_trend_analysis.

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?

No guidance on when to use this tool vs alternatives. Does not mention when to choose get_strategic_overview over get_strategy_brief, get_trend_analysis, or others in the sibling list.

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

Deploy Server

Other Tools