Skip to main content
Glama
Sign In
vic3-mcp

vic3-mcp

by kaisonlau8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pops

Analyze country population demographics from Victoria 3 save data, covering class, profession, culture, unemployment, and living standards.

Instructions

人口结构：阶层、职业、文化、失业、生活水平。

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

Input Schema

NameRequiredDescriptionDefault
countryNoplayer

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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. It does not explicitly state whether this is a read-only query, what side effects exist, what the default 'player' context means, or how data is returned. The described content hints at a read operation but does not disclose behavior.

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 phrase that lists the exact data categories covered, with no filler or redundancy. It is well-suited for quick scanning, though being only a fragment it leaves other dimensions underspecified.

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?

The tool is simple with one optional parameter and an output schema, so the description need not detail return values. However, it lacks usage guidance, parameter explanation, and explicit behavioral caveats, making it only a minimally complete description for an agent to select and call the tool correctly.

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%, and the description does not mention the 'country' parameter at all. The parameter name and default value are self-explanatory to some degree, but the description adds no meaning and fails to explain the special default 'player', leaving a significant compensation gap.

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 clearly identifies the resource as population structure and lists specific dimensions (class, occupation, culture, unemployment, living standards), which distinguishes it from adjacent tools like economy or politics. Although it lacks an explicit verb, the noun phrase is informative and not tautological.

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 about when to use this tool versus any sibling tool, nor any exclusion or alternative mention. The content description implies a demographic lookup, but the agent receives no explicit routing guidance or prerequisites.

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