Memory Cache Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_MEMORY | No | Maximum memory usage in bytes (100MB). Prevents excessive memory consumption. When exceeded, least recently used items are removed. | 104857600 |
| CONFIG_PATH | No | Path to a custom config.json file | |
| DEFAULT_TTL | No | Default time-to-live in seconds (1 hour). Items are automatically removed after this time. Prevents stale data from consuming memory. | 3600 |
| MAX_ENTRIES | No | Maximum number of items that can be stored in cache. Prevents cache from growing indefinitely. When exceeded, oldest unused items are removed first. | 1000 |
| CHECK_INTERVAL | No | Cleanup interval in milliseconds (1 minute). How often the server checks for expired items. | 60000 |
| STATS_INTERVAL | No | Stats update interval in milliseconds (30 seconds). How often cache statistics are updated. | 30000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_dataC | Store data in the cache with optional TTL |
| retrieve_dataC | Retrieve data from the cache |
| clear_cacheC | Clear specific or all cache entries |
| get_cache_statsC | Get cache statistics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Cache Statistics | Real-time cache performance metrics |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: clear_cache removes entries, get_cache_stats provides metrics, retrieve_data fetches data, and store_data saves data. There is no overlap or ambiguity between these operations.
Three tools use verb_noun naming (clear_cache, get_cache_stats, retrieve_data), which is consistent, but store_data uses a verb_noun pattern that slightly deviates from the others in verb choice. Overall, the naming is mostly predictable and readable.
With 4 tools, this server is well-scoped for a memory cache domain. Each tool serves a clear, essential function (store, retrieve, clear, stats), and no tool feels redundant or missing for basic cache operations.
The toolset covers core cache operations: store, retrieve, clear, and stats. A minor gap is the lack of an update or delete specific entry tool, but agents can work around this by clearing and re-storing. The surface supports basic workflows effectively.