Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

World Time

WorldTime
Read-only

World Time: World Time looks up the current local time, date, and timezone for any city, or for any latitude and longitude. Search by city name to get matching locations with country codes, IANA timezone identifiers, UTC offsets, and formatted times in 12-hour, 24-hour, and ISO 8601 formats. (Cost: 2 credits)

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": "WorldTime"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude of the location (-90 to 90)
lonNoLongitude of the location (-180 to 180)
cityNoThe city name for which you want to get the current time (e.g., New York)

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the cost (2 credits) and enumerates the returned fields: country codes, IANA timezone identifiers, UTC offsets, and 12-hour, 24-hour, and ISO 8601 formats. It does not discuss rate limits or ambiguous-city behavior, so it is strong but not exhaustive.

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 two compact sentences that front-load the core capability and then enumerate outputs and cost. There is minor redundancy in restating the tool name at the start ("World Time: World Time looks up..."), but otherwise every clause carries information.

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

Completeness4/5

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

An output schema exists, so the description need not explain return values, and it still outlines them at a high level. Combined with the 3-parameter schema and the cost disclosure, an agent has nearly everything needed; only the city-versus-coordinates precedence is left unstated.

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 coverage is 100%, so the schema already documents lat, lon, and city with ranges and examples; per the rubric this sets a baseline of 3. The description repeats that city search returns matching locations but adds no detail on precedence or interaction between city and coordinates, which are all optional (0 required).

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 pairs a specific verb ("looks up") with a precise resource (current local time, date, and timezone) and states both input modes, city or lat/lon. It does not distinguish itself from the nearby TimezoneLookup sibling, so it falls just short of a 5.

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?

Usage is implied: search by city name, or supply coordinates. There is no explicit when-to-use versus when-not guidance, and the existence of sibling tools such as TimezoneLookup and MeetingTimeConverter is never addressed, leaving the agent to infer routing.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources