Workflow 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 |
|---|---|
| mem_saveC | Record workflow memories with FIFO eviction (keep ≤ 1000 tokens) |
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's purpose is clearly defined as recording workflow memories with FIFO eviction, and no other tools exist to cause confusion.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'mem_save' follows a clear verb_noun pattern, which would be consistent if more tools were added.
One tool is too few for a server named 'Workflow MCP Server', which implies a broader scope for managing workflows. A single memory-saving tool does not provide the expected functionality for creating, managing, or executing workflows, making it an extreme mismatch for the apparent domain.
The tool surface is severely incomplete for a workflow server. It only offers memory saving with no tools for creating workflows, listing workflows, updating workflows, deleting workflows, or executing workflows. This leaves major gaps that will cause agent failures in handling workflow-related tasks.