Timezone By Location MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| api_endpointD | 请根据 RapidAPI 页面手动添加端点信息 |
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
The sole tool has an unclear purpose; its description is a placeholder asking to manually add endpoint info, providing no functional clarity. With ambiguous intent, agents cannot reliably select it.
The tool name 'api_endpoint' is a noun, not a verb-based action, and its description suggests configuration rather than a callable operation. No consistent pattern exists with only a single vague name.
A single tool is insufficient for a timezone-by-location service, and it is not even a functional tool but a placeholder, making the count inappropriate.
The server offers no actual timezone lookup functionality; the only tool is a stub, so the domain is entirely uncovered.