GetUTC 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_utc_timeA | Get accurate UTC time from multiple reliable sources |
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
There is only one tool, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
The single tool name follows a clear verb_noun pattern ('get_utc_time'), which is consistent and descriptive. With only one tool, consistency is basically perfect, though the sample size is too small to fully evaluate a pattern.
A single tool for fetching UTC time is extremely minimalcars could be argued as a simple utility, but it feels under-scoped for a server. Most MCP servers offer a set of related operations, so one tool is very thin and likely not worth the overhead.
The domain is time retrieval, but a single 'get time' tool provides no additional functionality like timezone conversion, formatting options, or historical time data. While it fulfills the basic need, it is severely limited and lacks common related operations.