Skip to main content
Glama
archi-max

civ6-mcp

by archi-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launch_game

Destructive

Starts Civilization VI through Steam and waits until the game reaches the main menu, ready for loading a saved game.

Instructions

Launch Civ 6 via Steam.

Starts the game and waits for the process to appear (~15-30 seconds).
The game will be at the main menu after launch — use load_save or
restart_and_load to load a specific save.

NOTE: FireTuner connection is NOT available at the main menu.
Only in-game MCP tools work after a save is loaded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.11

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds valuable behavioral details: the startup wait period, the fact that the game ends at the main menu, and the limitation that FireTuner (and thus in-game tools) only work after a save is loaded. No contradiction with annotations.

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?

Extremely concise: two sentences and a note. Every sentence provides critical information (action, behavior, limitations). Front-loaded with the main purpose. No redundant or extraneous content.

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

Completeness5/5

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

For a zero-parameter tool with an output schema (implied but not shown), the description covers all necessary context: what it does, how it behaves (wait time), what state the game is in after launch, and what tools work afterwards. Sibling tools are hinted at, providing sufficient completeness.

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 has 0 parameters, so the schema is fully described (100% coverage). The description adds no parameter info, which is acceptable; baseline for 0 params is 4. No additional semantic explanation needed.

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?

The description explicitly states the tool launches Civ 6 via Steam. It uses a specific verb ('Launch') and resource ('Civ 6'), distinguishing it from sibling tools like load_save and restart_and_load, which are mentioned as after-launch actions.

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

Usage Guidelines5/5

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

Provides clear when-to-use context (launching the game) and explicitly states that FireTuner is not available at the main menu, directing users to use load_save or restart_and_load instead. Also mentions expected wait time (~15-30 seconds), guiding agent expectations.

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