World Time By Api Ninjas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for API Ninjas World Time API |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1worldtimeB | API Ninjas World Time API endpoint. Returns the current date and time by city/state/country, location coordinates (latitude/longitude), or timezone. One of the following parameter combinations must be set: lat + lon, city (state and country optional), timezone |
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 ambiguity or overlap between tools. The single tool 'v1worldtime' has a clear and distinct purpose: retrieving world time data based on various location parameters.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'v1worldtime' follows a clear pattern (version prefix + descriptive name) and does not conflict with any other naming conventions.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. While this tool covers world time retrieval comprehensively, the server's scope feels thin with only one operation, which may hinder agent workflows that require more diverse interactions.
For the domain of world time retrieval, the tool provides robust coverage with support for city/state/country, coordinates, and timezone inputs. However, there are minor gaps, such as lacking tools for timezone conversion, historical time data, or batch queries, which could limit advanced use cases.