MCP-Wait
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port number when using SSE transport type | 8080 |
| TRANSPORT_TYPE | No | The transport type for the MCP server (stdio or sse) | stdio |
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 |
|---|---|
| waitB | Wait for a specified number of seconds, useful for waiting for other tasks to finish |
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 confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, it inherently follows a consistent naming pattern with itself. The name 'wait' is straightforward and matches the verb_noun style, though no pattern can be assessed across multiple tools.
A single tool is generally too few for most server purposes, as it limits functionality and suggests a very narrow scope. While the tool is useful for waiting, it lacks companion tools for broader task management or integration, making the server feel incomplete.
The server's purpose appears to be related to task management or timing, but with only a 'wait' tool, there are significant gaps. There are no tools for starting, monitoring, or canceling tasks, making the surface severely incomplete for any practical workflow.