Knowledge Graph Memory Server
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 |
|---|---|
| create_entitiesB | Create multiple new entities in the knowledge graph |
| create_relationsC | 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_observationsC | Delete specific observations from entities in the knowledge graph |
| delete_relationsB | Delete multiple relations from the knowledge graph |
| read_graphB | Read the entire knowledge graph |
| search_nodesB | Search for nodes in the knowledge graph based on a query |
| open_nodesB | 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, but 'open_nodes' and 'search_nodes' could cause some confusion as both involve accessing nodes, though 'open_nodes' seems to retrieve specific nodes by name while 'search_nodes' queries based on criteria. The CRUD operations for entities, relations, and observations are clearly separated, reducing major overlap.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'add_observations', 'create_entities', and 'delete_relations'. This predictability makes it easy for agents to understand and use the tool set without confusion from mixed conventions.
With 9 tools, the server is well-scoped for managing a knowledge graph, covering core operations like creation, deletion, reading, and searching. This count is appropriate as it provides comprehensive functionality without being overwhelming or too sparse for the domain.
The tool set offers strong coverage with CRUD operations for entities, relations, and observations, plus reading and searching capabilities. A minor gap is the lack of update tools for entities or relations, which might require workarounds like delete-and-recreate, but core workflows are well-supported.