graymatter
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkpoint_resumeB | Restore the latest checkpoint for an agent. |
| checkpoint_saveA | Save a checkpoint of current agent state. |
| memory_addB | Store a new fact in GrayMatter memory. |
| memory_reflectA | Add, update (supersede), forget, link, or pin your memories. Use when you notice a contradiction, finish a task, learn a durable preference that should persist, or the user declares something permanent (a standing obligation, an architecture decision) that must never decay. |
| memory_searchA | Search GrayMatter memory for relevant facts. Call once for your agent_id, then again with agent_id "shared" for user-level preferences. |
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 5 tools
Checkpoint and memory tools are cleanly separated by domain, and memory_search is distinct. However, memory_add and memory_reflect both include adding memories, which could cause an agent to choose the wrong one for a simple fact.
All tool names follow a consistent noun_verb snake_case pattern: checkpoint_resume, checkpoint_save, memory_add, memory_reflect, memory_search. The convention is uniform and predictable.
Five tools is well-scoped for a memory and checkpointing server. Each tool addresses a clear operational need without unnecessary bloat.
The set covers checkpoint save/resume and the core memory operations: add, search, update/supersede, forget, link, and pin. No major lifecycle gaps are apparent for the stated purpose.