Skip to main content
Glama
Sign In
vic3-mcp

vic3-mcp

by kaisonlau8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_save

Load a Victoria 3 save by name or full path, enabling immediate access to its content for analysis and strategic recommendations.

Instructions

融化并载入一个 .v3 存档。name 可以是存档名（如 Qing_MCP）或完整路径。

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

Input Schema

NameRequiredDescriptionDefault
langNosimp_chinese
nameNoQing_MCP

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It says the tool 'melts and loads' a save but does not state whether loading replaces the current session state, requires a prior save listing, has side effects, or how invalid paths are handled.

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?

The description is a single compact sentence that places the core action first. It contains no filler, but the word '融化' is ambiguous and could confuse agents despite being short.

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

Completeness2/5

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

Although an output schema exists, the description is too thin for a state-changing load operation in a tool suite with clear workflow siblings. It does not explain where loading fits in the workflow, what happens to the currently loaded save, or how this interacts with list_saves.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It adds useful meaning for 'name' (save name or full path, with example), but 'lang' is left completely undocumented and its role is not mentioned anywhere.

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 names a specific verb ('load') and a specific resource ('.v3 save'), and explains what 'name' refers to with an example. However, '融化' is an unexplained metaphor, and the description does not explicitly distinguish this tool from siblings like list_saves or search_save.

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 is given about when to use this tool versus alternatives, such as list_saves to find available saves or search_save to locate content. The only usage hint is how to specify 'name', which is parameter-level guidance rather than contextual usage guidance.

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