Memory Store MCP 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_webC | Search the web using Google |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_web' has a single, distinct purpose that cannot be confused with any other tool in this set.
The single tool name follows a clear verb_noun pattern ('search_web'), and since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'Memory Store MCP Server', which implies functionality related to storing, retrieving, or managing memory data. The tool 'search_web' does not align with this domain, making the count inappropriate and mismatched with the apparent scope.
The tool set is severely incomplete for the inferred domain of memory storage. There are no tools for creating, reading, updating, or deleting memory entries, which are essential operations for a memory store, leaving significant gaps that will cause agent failures.