Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STELLARIS_KB_DIRNoThe desired writable knowledge directory. Without it, storage defaults to a sibling .kb directory.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
stellaris_explainA

ONE-CALL answer to "what does X mean?". Searches the knowledge base, returns a digest of the best-matching wiki page(s) plus glossary and related-page hits. Use this first for any Stellaris term, UI label, resource, job, ship part, crisis or mechanic.

stellaris_searchA

BM25 full-text search across every downloaded wiki page AND every video transcript chunk. Returns ranked titles with snippets, kind of source, and (for video) a timestamped deep link.

stellaris_video_searchA

Search the Stellaris video transcripts in the KB. Returns the spoken content with a deep link straight to that moment in the video (e.g. &t=6393s). Use when a player would rather watch an explanation, or when the wiki page is too dry.

stellaris_video_chaptersA

List the chapters of an ingested video with timestamps and deep links. Use to point a player at the right section of a long tutorial.

stellaris_get_pageA

Fetch the full text of a wiki page from the local KB. Optionally narrow to one section by heading name.

stellaris_outlineA

List the section headings of a page. Cheap way to see what a big page contains before reading it.

stellaris_relatedC

Pages linked from a given page (the "what should I read next" graph).

stellaris_glossaryA

Look up Stellaris slang and abbreviations (FE, AE, GC, ecum, naval cap, tall/wide, CG...). Explains community shorthand a new player will not know.

stellaris_ui_hintA

Map a UI label / tooltip / resource name seen in a screenshot to the wiki page that explains it. Call this when the user pastes a screenshot and you can read text off it.

stellaris_learning_pathA

Ordered reading list for a topic. Use when teaching a beginner or when the user asks "where do I start / how do I learn X".

stellaris_kb_statsA

Knowledge base coverage: how many pages are downloaded, indexed tokens, and how many titles are still queued.

stellaris_kb_add_pageA

Store a wiki page into the local KB from raw wikitext. Call this right after fetching https://stellaris.paradoxwikis.com/index.php?title=&action=raw with WebFetch. The page becomes searchable instantly and offline.

stellaris_queue_nextB

Get the next batch of wiki page titles that still need to be downloaded. Drives the crawling cron job.

stellaris_queue_addB

Add titles to the download queue, optionally into a priority tier (1 = highest).

stellaris_live_fetchA

Attempt a live download of a wiki page. Usually returns blocked:true because of the site bot challenge; when it does, follow the returned workaround (WebFetch + stellaris_kb_add_page).

stellaris_readmeA

Read the MCP server README: architecture, the bot-challenge workaround, and the teaching contract for answering player questions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
stellaris-wiki READMEArchitecture, bot-challenge workaround, teaching contract.
Stellaris slang glossary

TDQS

A3.5/5.0

Scored across 16 tools

Disambiguation4/5

Most tools have clearly distinct roles (explain vs search vs glossary vs video_search), and descriptions explicitly steer between them. The main overlap is stellaris_search (which covers video too) versus stellaris_video_search, and stellaris_explain versus stellaris_search, but the descriptions differentiate them reasonably well.

Naming Consistency4/5

All tools share the stellaris_ prefix and snake_case, which makes the set predictable. There is some mixing of verb-led (explain, search, get_page) and noun-led (glossary, outline, readme, learning_path) names, but the pattern remains readable.

Tool Count4/5

16 tools is slightly on the heavy side but justified by the server's three concerns: KB querying, crawling/ingestion management, and teaching aids. Each tool earns its place, with no obvious filler.

Completeness4/5

The KB lifecycle is mostly covered: add, search, fetch, outline, related, stats, and queue management. Minor gaps exist around update/delete/re-index of stored pages, which agents can work around by re-adding content.