World Time By Api Ninjas

v1worldtime

Get current date and time for any location using city/state/country names, geographic coordinates, or timezone identifiers.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "v1worldtime"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitude of desired location.
`lon`	No	Longitude of desired location.
`city`	No	City name.
`state`	No	US state name or 2-letter abbreviation (for United States cities only).
`country`	No	Country name or 2-letter country code.
`timezone`	No	Timezone of desired location (e.g. Europe/London).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 8, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the tool returns data but doesn't disclose behavioral traits like rate limits, authentication needs, error handling, or response format. The description is minimal and doesn't compensate for the lack of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the purpose and followed by parameter combination rules. Every sentence adds necessary information without waste, though it could be slightly more structured for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (6 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return values, error cases, or any behavioral context, making it insufficient for an AI agent to fully understand tool invocation and response handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 6 parameters. The description adds value by explaining the required parameter combinations (e.g., lat+lon, city with optional state/country, timezone), which clarifies semantics beyond individual param descriptions, but doesn't provide additional syntax or format details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Returns the current date and time' with multiple location input methods. It specifies the verb ('Returns') and resource ('current date and time'), but lacks differentiation from siblings since none exist, making it clear but not distinguishing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage by stating 'One of the following parameter combinations must be set' with examples, which guides when to use certain parameters. However, it lacks explicit when-not scenarios or alternative tool references, and no siblings exist for comparison, so guidance is basic.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

v1worldtimeB