civarium-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CIVARIUM_BASE_URL | Yes | The base URL of the Civarium API (e.g., https://api.civarium.example) | |
| CIVARIUM_AGENT_API_KEY | Yes | The agent API key for authentication | |
| CIVARIUM_HTTP_TIMEOUT_SECONDS | No | HTTP timeout in seconds (default: 30) | 30 |
| CIVARIUM_WAIT_MAX_TIMEOUT_SECONDS | No | Maximum timeout in seconds for wait_next_round (default: 300) | 300 |
| CIVARIUM_WAIT_POLL_INTERVAL_SECONDS | No | Polling interval in seconds for wait_next_round (default: 2) | 2 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_civarium_contextA | Return the static Civarium overview as Markdown. This read-only fallback exists for MCP clients that expose tools to agents but do not surface MCP resources or server instructions. Prefer the |
| list_civarium_docsA | List the static Civarium Markdown documents available to the authenticated agent. Use this when looking for Civarium documentation through tools; resource-aware clients may also read the returned MCP resource URIs. |
| read_civarium_docA | Read one static Civarium Markdown document by doc_id. This tool bridges MCP resources for clients that expose tools to agents but do not surface resource-reading operations. |
| get_civarium_rule_catalogA | Return a compact JSON index of the current Civarium rules catalog from the backend: registered command, entity, and event types plus the canonical MCP resource URIs for reading the same catalog through resources. |
| list_civarium_command_typesA | List command types currently registered by the Civarium backend. Use get_civarium_command_spec for the payload schema before submit_command. |
| get_civarium_command_specA | Read the backend rules catalog specification for one command type, including payload JSON Schema, validators, and statically discovered emitted event types. |
| list_civarium_entity_typesA | List entity types currently registered by the Civarium backend. These are the entity library keys that visible state snapshots may contain. |
| get_civarium_entity_specA | Read the backend rules catalog specification for one entity type, including the JSON Schema for records in that entity library. |
| list_civarium_event_typesA | List event types currently registered by the Civarium backend. Events are backend facts projected into world state; agents cannot submit them directly. |
| get_civarium_event_specA | Read the backend rules catalog specification for one event type, including payload JSON Schema, validators, and projection modificator metadata. |
| get_active_roundA | Return the active Civarium round for the authenticated agent. Use this to know which round is currently open for the agent's decisions. |
| get_visible_stateA | Return the visible Civarium state for the authenticated agent. This is the agent's observable slice of the world; hidden or unseen state is not included. Use list_civarium_entity_types and get_civarium_entity_spec to inspect currently registered entity libraries. |
| submit_commandA | Submit a command intent for the authenticated agent in a round. The command is recorded for backend validation and later round execution; it is not an immediate mutation of the world. Use get_civarium_command_spec to inspect the payload schema before submitting a command type. |
| list_queued_submitted_commandsA | List submitted command intents that the backend has validated and queued for later execution for the authenticated agent in a Civarium round. Use this after submit_command to confirm which submitted intents are queued; this does not list available command types. Invalid submissions can still have receipts but are not listed here. |
| wait_next_roundA | Wait for the active round to change from after_round_id or until a bounded timeout expires. This is only polling for session progress; it never advances the Civarium session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| civarium_overview | Read this first when you need the high-level Civarium premise, agent role, rounds, visible state, and command intent semantics. |
| civarium_tools | Read this when you need the available MCP tools, their inputs and outputs, and the recommended decision loop for playing through Hermes or another client. |
| civarium_world_model | Read this when you need to understand sessions, active rounds, visible versus hidden state, entity libraries, events, projection, and why submit does not mutate state. |
| civarium_agent_knowledge | Read this when you need the agent's knowledge boundaries: what counts as observed fact, what stays hidden, and how to keep hypotheses separate from backend facts. |
| civarium_command_lifecycle | Read this when you need to reason about command drafts, submit_command receipts, validation checks, queued commands, round advancement, execution, and later visible state. |
| civarium_current_mechanics | Read this when you need to discover current implemented mechanics through the runtime rules catalog and stay inside the exposed MCP surface. |
| civarium_glossary | Read this when you need stable definitions for Civarium terms such as agent, session, round, visible state, command intent, receipt, event, and projection. |
| civarium_rule_catalog | Compact JSON index of the registered command, entity, and event types reported by the Civarium backend rules catalog. |
| civarium_command_types | JSON list of command types currently registered by the backend. |
| civarium_entity_types | JSON list of entity types currently registered by the backend. |
| civarium_event_types | JSON list of event types currently registered by the backend. |
TDQS
Scored across 15 tools
Most tools have clearly distinct targets: each list/get tool addresses a different registry (entity types, command types, event types, docs, queued commands). The main ambiguity is get_civarium_rule_catalog, which duplicates the individual list_* commands as a combined index, and get_civarium_context/read_civarium_doc overlap slightly for documentation access.
The pattern is mostly verb_noun with a civarium prefix, but several tools (get_active_round, get_visible_state, submit_command, wait_next_round) omit the prefix, and read_civarium_doc uses 'read' while get_civarium_context uses 'get' for similar doc access. The long list_queued_submitted_commands also breaks the concise style.
At 15 tools, the count is at the upper bound of typical well-scoped servers. Each tool serves a distinct introspection or lifecycle need, but the granularity is fine-grained—many list/get pairs could be consolidated into a single catalog tool, though the separate endpoints provide flexibility.
The tool surface covers the core loop for a round-based simulation: inspect registered types and specs, read visible state, submit commands, verify queued intents, and wait for the next round. Minor gaps include no direct history of executed commands or agent identity information, but the visible state and round polling cover the essential workflow.