Skip to main content
Glama
2962348318-del

Civ6 MCP CN

by 2962348318-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

write_strategic_summary

Compress recent game history into a compact strategic summary that persists to disk, enabling long-term memory and continuity across turns and session restarts.

Instructions

Write a strategic summary for long-term memory.

Call this every 5-10 turns to compress recent history into a compact
strategic context. This persists to disk and survives session restarts.

Args:
    turn: Current turn number.
    summary: 2-3 sentences summarizing your empire state and situation.
    goals: Current long-term goals (victory target, expansion plans).
    threats: Major threats (hostile neighbors, barbarians, resource gaps).
    opportunities: Current opportunities (weak neighbors, settle spots).
    key_decisions: Important recent decisions and their rationale.

Returns:
    Confirmation string.

Input Schema

NameRequiredDescriptionDefault
turnYes
goalsNo
summaryYes
threatsNo
key_decisionsNo
opportunitiesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond the readOnlyHint=false annotation: it persists to disk, survives session restarts, and returns a confirmation string. It does not discuss whether repeated writes overwrite previous summaries, but the key mutating behavior is disclosed.

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?

The description is front-loaded with purpose and cadence, then uses a compact Args and Returns structure. Every sentence and field explanation earns its place, with no redundant restatement of the name.

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 six-parameter write tool with 0% schema description coverage, the description fully compensates by explaining all arguments and the return value. The annotations are minimal but the description supplies the behavioral details an agent needs to invoke it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden. It documents all six parameters with meaningful semantics, including what each field should contain and which are required versus optional under the Args section.

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 states a specific verb and resource: write a strategic summary for long-term memory. It clearly distinguishes this from ordinary turn actions by explaining that it compresses recent history into persistent strategic context, though it does not explicitly mention the sibling read_strategic_summary.

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

Usage Guidelines4/5

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

The cadence is explicit: 'Call this every 5-10 turns' and it says to use it to compress recent history. It gives clear usage context but does not name alternatives or conditions where calling it would be inappropriate.

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