whattimeisit-mcp
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 |
|---|---|
| what_time_is_itB | Returns the current time string based on the client's IP using World Time API. |
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. The tool's purpose is singular and clearly defined, making disambiguation trivial.
The single tool name 'what_time_is_it' follows a clear verb-based pattern. Since there are no other tools to compare against, consistency is inherently perfect.
A single tool is too few for most practical server purposes, as it severely limits functionality and flexibility. For a time-related server, this feels thin and under-scoped.
The server's domain appears to be time-related, but with only one tool to get the current time, there are significant gaps. Missing operations include time zone conversions, scheduling, or historical time queries, which are common in time-based services.