synapsen-mcp
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 |
|---|---|
| state_readB | Aktueller innerer Zustand: Botenstoffe, abgeleitete Gefühlslagen, Bindung, Ermüdung. |
| state_promptC | Derselbe Zustand als fertiger System-Prompt-Zusatz. Vor einer Antwort lesen und voranstellen. |
| state_eventB | Ein benanntes Ereignis melden. Der Zustand verändert sich daraufhin von selbst. |
| state_injectA | Feinsteuerung: einen einzelnen Botenstoff verändern. Im Normalfall lieber state_event nutzen. |
| state_settleB | Sanft Richtung Ruhewert regulieren. Kein harter Reset. |
| state_whyA | Führt den aktuellen Zustand auf seine Ursachen zurück: welche Ereignisse, welcher Tagesrhythmus, welche Kopplung. Für Fehlersuche und Nachvollziehbarkeit. |
| state_historyC | Die zuletzt protokollierten Ereignisse. |
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 7 tools
Each tool has a distinct role: reading, formatting as prompt, event-driven updates, fine-grained injection, settling, explaining causes, and history. The only mild overlap is between state_read and state_prompt, but the descriptions clarify that one is raw state and the other is a ready-to-use prompt fragment.
All tools consistently use the state_ prefix and lowercase naming. Some entries use nouns or adverbs instead of verbs, but the pattern is predictable and easy to navigate.
Seven tools is a well-scoped size for this state-management domain. Each tool provides a meaningful capability without unnecessary bloat or missing core functionality.
The set covers reading state, using it in prompts, updating via events, fine-grained adjustment, settling, causal tracing, and viewing history. A hard reset or history-clearing operation is absent, but the deliberate design avoids it and the core lifecycle is well covered.