Calyx 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_code_reflexA | Instant (<1ms) associative memory check of proposed code against past rewarded or punished bug patterns. Returns 'avoid', 'safe', or 'neutral'. |
| remember_code_outcomeB | Applies one-shot dopamine reward (test passed) or punishment (test failed/bug) to Mushroom Body synaptic weights. |
| query_associative_memoryB | Searches stored code patterns using Fly-LSH sparse binary Hamming similarity. |
| inspect_memory_stateA | Returns total active memories, synaptic weight distribution, and health statistics of the Mushroom Body. |
| reset_memoryA | Resets or prunes the synaptic weights and associative memory back to baseline. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Calyx Synaptic Health | Live Mushroom Body synaptic weight statistics |
TDQS
Scored across 5 tools
Each tool has a distinct role: querying memory, checking code reflexes, inspecting state, learning outcomes, and resetting. The only mild overlap is between query_associative_memory and check_code_reflex, since both access stored patterns, but their purposes are clearly separated by general search versus instant classification.
All tool names follow a consistent verb_noun snake_case pattern: query_, check_, inspect_, remember_, and reset_. The naming clearly communicates the action and target for every tool.
Five tools is well-scoped for a memory system server. Each tool covers a necessary operation without redundancy or bloat.
The tool set covers the full lifecycle of associative memory: querying, fast checking, inspecting state, learning from outcomes, and resetting/pruning. No obvious dead ends or missing critical operations exist for the stated purpose.