Knowledge Graph Memory Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_FILE_PATH | No | Path to the memory storage JSON file (default: memory.json in the server directory) | memory.json |
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 |
|---|---|
| create_entitiesC | Create multiple new entities in the knowledge graph |
| create_relationsB | Create multiple new relations between entities in the knowledge graph. Relations should be in active voice |
| add_observationsB | Add new observations to existing entities in the knowledge graph |
| delete_entitiesA | Delete multiple entities and their associated relations from the knowledge graph |
| delete_observationsB | Delete specific observations from entities in the knowledge graph |
| delete_relationsA | Delete multiple relations from the knowledge graph |
| read_graphB | Read the entire knowledge graph |
| search_nodesA | Search for nodes in the knowledge graph based on one or more keywords. The search covers entity names, types, subdomains, and observation content. Multiple keywords are treated as OR conditions, where any keyword must match somewhere in the entity's fields. |
| open_nodesA | Open specific nodes in the knowledge graph by their names. Returns the complete node information including subdomain and all metadata. |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity: create/delete operations target specific components (entities, relations, observations), while read/search/open handle different access patterns. The descriptions reinforce these distinctions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., add_observations, delete_relations, search_nodes). The naming is predictable and readable, with no deviations in style or convention.
With 9 tools, the server is well-scoped for a knowledge graph memory system. Each tool earns its place by covering essential CRUD operations and access methods, avoiding both bloat and insufficiency for the domain.
The toolset provides strong coverage for core knowledge graph operations, including creation, deletion, reading, and searching. A minor gap exists in update capabilities for entities or observations, which agents might need to work around by deleting and recreating, but overall workflows are well-supported.