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
} |
| 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_memoryC | 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_memoryC | 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 action: check_code_reflex evaluates proposed code, query_associative_memory performs raw similarity search, remember_code_outcome writes, inspect_memory_state reports stats, and reset_memory clears. The only mild overlap is between check_code_reflex and query_associative_memory, both of which read the associative store, but their input/output contracts differ enough to disambiguate.
All five names are snake_case verb_noun constructions (check_code_reflex, remember_code_outcome, query_associative_memory, inspect_memory_state, reset_memory), giving a predictable pattern. Minor deviation: reset_memory and inspect_memory_state drop the '_code_' qualifier used by the others, but readability remains high.
Five tools is well-scoped for a lightweight associative memory service, with each tool mapping to a clear lifecycle operation (write, read, evaluate, inspect, reset). No redundant or filler tools are present.
The surface covers the full memory lifecycle: write (remember_code_outcome), read/search (query_associative_memory, check_code_reflex), introspection (inspect_memory_state), and deletion (reset_memory). Minor gaps like bulk import/export or targeted single-memory deletion exist but are not blocking for the stated purpose.