christina
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cpg_queryC | CPG & AST radar: def-use chains, CFG, virtual interfaces, blast radius. |
| rlm_executeC | Sandboxed RLM REPL executor with transactional CoW rollback, 3-phase EGRI linter, governor. |
| memory_evolveC | Semantic memory: AGM revision, GC, distill_global, query_global, search, persist. |
| swarm_blackboardD | Swarm blackboard & OCC concurrency: Kung-Robinson OCC validation, Tree-CRDT 3-way merge, Linda tuple space. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a completely different subsystem: static code analysis, sandboxed execution, semantic memory, and concurrency/blackboard coordination. There is no overlap or plausible confusion between them.
All tools follow a readable two-part snake_case format with domain-specific prefixes. However, the suffixes mix verbs (query, execute, evolve) with a noun (blackboard), creating a minor deviation from a fully uniform pattern.
Four tools is a reasonable, focused count for a server whose scope appears to be a coordinated agent runtime: analyze, execute, remember, and coordinate. Each tool earns its place and none feel redundant.
The tool surface covers the major capabilities one would expect from this kind of system: code understanding, safe execution, memory persistence, and shared-state coordination. There are minor gaps such as explicit file/API interaction, but the broad sub-operations embedded in each tool make the overall surface feel fairly complete.