MCP Wait Timer 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 |
|---|---|
| waitA | Waits for a specified duration in seconds. |
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 for ambiguity or overlap between tools. The tool 'wait' has a single, clear purpose that cannot be confused with any other tool in this set.
The naming is trivially consistent as there is only one tool. The tool name 'wait' follows a simple verb pattern, and there are no other tools to create inconsistency or mixed conventions.
A single tool is too few for most server purposes, making the server feel thin and limited in scope. While a timer server might logically have few tools, one tool is borderline minimal and may not cover all expected timer-related operations, such as cancelling or listing waits.
The tool set is severely incomplete for a timer server. It only provides a wait function, missing obvious operations like cancelling an active wait, checking wait status, or managing multiple timers, which are common in timer-related domains.