Skip to main content
Glama
thomandretti

ck3-strategy-advisor

by thomandretti

Realm Overview

realm_overview
Read-only

Get a snapshot of your ruler and realm: title, house, gold, prestige, piety, and date. Use this to understand your current situation before making strategic decisions.

Instructions

Snapshot of the player's ruler and realm: name, primary title & tier, house, gold, prestige, piety, and in-game date. Start here for 'what's my situation'. For military/wars use military; for heirs use succession.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, so description adds context beyond that by specifying returned data (ruler, realm, stats) and framing it as a snapshot, implying no side effects.

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?

Three concise sentences with front-loaded content: first lists data, second provides usage, third gives alternatives. No extraneous words.

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 no parameters and no output schema, description adequately explains purpose and usage. Minor lack of detail on output format (e.g., single object vs list) but sufficient for a simple snapshot tool.

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?

No parameters exist (0 params, 100% schema coverage), so baseline is 4. Description does not need to add param info and correctly omits it.

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?

Clearly states it provides a snapshot of the player's ruler and realm, listing specific fields (name, title, house, gold, etc.). Distinguishes from siblings by referencing military and succession tools.

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?

Explicitly says 'Start here for 'what's my situation'' and directs to 'military' for wars and 'succession' for heirs, providing clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thomandretti/ck3-strategy-advisor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server