maps-mcp

Overview Schema Source Related Servers Discussions Admin

time_zone

Get the IANA time zone and UTC offset (including DST) for any coordinates. Provide a Unix timestamp to evaluate DST at a specific moment; 0 gives the current time.

Instructions

IANA time zone + UTC offset (incl. DST) at coordinates. timestamp (unix epoch seconds) evaluates DST at a specific moment; 0 = now.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "time_zone"
  }
}

Input Schema

Name	Required	Description	Default
`latitude`	Yes
`longitude`	Yes
`timestamp`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral detail about how the timestamp parameter evaluates DST at a specific moment and that 0 means 'now', which is not visible in the schema. However, it does not disclose error behavior or side effects (unlikely for a read-only tool).

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

Conciseness5/5

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

The description is two sentences, front-loaded with the primary purpose and immediately followed by the timestamp nuance. Every word earns its place with no redundancy.

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

Completeness5/5

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

The tool is simple and an output schema exists, so return values need not be described. The description covers the essential behavior, including the optional timestamp explanation, making it complete for an agent to use correctly.

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 0%, so the description must compensate. It explains the timestamp parameter's meaning well (unix epoch seconds, DST evaluation, 0=now), but latitude and longitude are not described beyond their parameter names, which are self-evident. Partial compensation yields a mid-range score.

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

Purpose5/5

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

The description clearly states the tool returns IANA time zone and UTC offset (including DST) for given coordinates, which is a specific and distinct capability compared to siblings like geocode or travel_time. The resource and action are unambiguous.

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

Usage Guidelines4/5

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

The description implies the use case: obtain time zone data for a coordinate. It gives clear context but does not explicitly mention when not to use it or alternative tools. Thus it is clear but lacks explicit exclusions.

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

Deploy Server