Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Time zone at a point

time_zone_at_point
Read-onlyIdempotent

What time zone is a latitude/longitude in, and what time is it there now? The IANA zone of the nearest populated place, the UTC offset now and whether DST is on. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "time_zone_at_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, decimal degrees (-90 to 90).
lngYesLongitude, decimal degrees (-180 to 180).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the meaningful nuance that the zone is derived from the *nearest populated place* rather than a polygon boundary — a real semantic caveat an agent needs — plus that the current offset and DST state are included. It omits edge behavior for remote/ocean coordinates.

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

Conciseness3/5

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

The first two sentences are well front-loaded and information-dense. The closing promotional sentence pointing at the vendor's other APIs adds no value for tool selection or invocation and is pure noise in a two-sentence definition.

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?

With no output schema, the description does the necessary work of naming what comes back: IANA zone, current UTC offset, and DST status. What remains unstated is behavior for coordinates far from any settlement or in open water, which matters given the 'nearest populated place' resolution strategy.

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%; lat and lng are each documented with type and valid ranges in the schema. The description only restates that the input is a latitude/longitude pair and adds no parsing or format detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource in question form (time zone for a latitude/longitude plus current local time), and enumerates the concrete outputs: IANA zone, current UTC offset, DST flag. It does not name or contrast any sibling tool (e.g., convert_coordinates or find_city), so it stops short of full disambiguation.

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 only implied by the framing question — an agent can infer this is the tool for 'what zone/time is at this coordinate.' There is no explicit when-to-use, when-not, or pointer to related tools such as coordinate conversion or city lookup, so guidance is adequate but thin.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources