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 JSONL file (default: memory.jsonl in the server directory) | memory.jsonl |
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_entitiesB | 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_nodesC | Search for nodes in the knowledge graph based on a query |
| open_nodesC | Open specific nodes in the knowledge graph by their names |
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
Most tools have distinct purposes targeting specific operations like adding/deleting observations, entities, or relations, and reading/searching the graph. However, 'open_nodes' and 'search_nodes' could be confused as both involve finding nodes, though 'open_nodes' seems to retrieve specific nodes by name while 'search_nodes' queries based on content.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'add_observations', 'create_entities', and 'delete_relations'. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 9 tools, the server is well-scoped for managing a knowledge graph, covering core operations like CRUD for entities, relations, and observations, as well as reading and searching. This count is appropriate and each tool appears to earn its place without being overwhelming.
The tool set provides comprehensive coverage for basic knowledge graph operations, including creation, deletion, reading, and searching. A minor gap is the lack of update tools for entities, relations, or observations, which might require workarounds like delete-and-recreate, but core workflows are well-supported.