Skip to main content
Glama

geo

by io.github.pipeworx-io

Get Timezone

get_timezone
Read-onlyIdempotent

Look up the IANA timezone name, current local time, and UTC offset (hours) for a given latitude and longitude via TimeAPI.io. Requires coordinates — does not accept city names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude
longitudeYesLongitude

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneYesIANA timezone name
local_timeYesCurrent local time in ISO format
utc_offset_hoursYesUTC offset in hours (may include decimal for minutes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "latitude": 51.5074,
+    "longitude": -0.1278
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "local_time": {
+      "description": "Current local time in ISO format",
+      "type": "string"
+    },
+    "timezone": {
+      "description": "IANA timezone name",
+      "type": "string"
+    },
+    "utc_offset_hours": {
+      "description": "UTC offset in hours (may include decimal for minutes)",
+      "type": "number"
+    }
+  },
+  "required": [
+    "timezone",
+    "local_time",
+    "utc_offset_hours"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "_apiKey": "your-geonames-api-key",
-    "lat": 40.7128,
-    "lng": -74.006
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "country_code": {
-      "description": "ISO country code",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "country_name": {
-      "description": "Full country name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "current_time": {
-      "description": "Current local time at location",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "dst_offset": {
-      "description": "Daylight saving time offset",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "gmt_offset": {
-      "description": "Current GMT offset in hours",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "latitude": {
-      "description": "Latitude coordinate",
-      "type": "number"
-    },
-    "longitude": {
-      "description": "Longitude coordinate",
-      "type": "number"
-    },
-    "raw_offset": {
-      "description": "Raw offset from GMT",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "sunrise": {
-      "description": "Sunrise time",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sunset": {
-      "description": "Sunset time",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "timezone_id": {
-      "description": "IANA timezone identifier",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "timezone_id",
-    "gmt_offset",
-    "raw_offset",
-    "dst_offset",
-    "current_time",
-    "sunrise",
-    "sunset",
-    "country_code",
-    "country_name",
-    "latitude",
-    "longitude"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country_code": {
+      "description": "ISO country code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country_name": {
+      "description": "Full country name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "current_time": {
+      "description": "Current local time at location",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dst_offset": {
+      "description": "Daylight saving time offset",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "gmt_offset": {
+      "description": "Current GMT offset in hours",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "latitude": {
+      "description": "Latitude coordinate",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Longitude coordinate",
+      "type": "number"
+    },
+    "raw_offset": {
+      "description": "Raw offset from GMT",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "sunrise": {
+      "description": "Sunrise time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sunset": {
+      "description": "Sunset time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timezone_id": {
+      "description": "IANA timezone identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "timezone_id",
+    "gmt_offset",
+    "raw_offset",
+    "dst_offset",
+    "current_time",
+    "sunrise",
+    "sunset",
+    "country_code",
+    "country_name",
+    "latitude",
+    "longitude"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-geonames-api-key",
+    "lat": 40.7128,
+    "lng": -74.006
+  }
+]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable context beyond these: it discloses dependency on an external service (TimeAPI.io) and a hard input constraint (requires coordinates, not city names), which helps the agent understand potential failure modes and appropriate usage.

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 with no redundancy: the first states the purpose and outputs, the second clearly states the input requirement and exclusion. Every word serves a functional role, making it appropriately concise and front-loaded.

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 (2 params, read-only, with output schema) and the description fully covers its purpose, inputs, and constraints. The annotations and output schema handle safety and return structure, so the description does not need to elaborate further. It is complete for an agent to select and invoke 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 100%, so the baseline is 3. The description reiterates that parameters are coordinates but adds little beyond the schema's minimal 'Latitude'/'Longitude' text. The schema examples (e.g., 40.7128, -74.006) provide typical format guidance, but the description itself does not significantly enhance parameter meaning beyond reinforcing the coordinate requirement.

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 uses a specific verb ('Look up') and precisely identifies the resource (IANA timezone name, current local time, UTC offset) for a given latitude/longitude. It also distinguishes itself from siblings by explicitly stating it does not accept city names, which is a key differentiator from geocoding tools in the sibling list.

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

Usage Guidelines5/5

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

The description provides an explicit when-to-use ('for a given latitude and longitude') and when-not-to-use ('does not accept city names'). This exclusion clearly signals to the agent that if city names are available, another tool (e.g., geocode) should be used instead, even though no alternative is named.

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

All geo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Multiple tools serve overlapping purposes, especially ask_pipeworx and ask_pipeworx_beta (explicitly identical) and ask_pipeworx_grounded/deep_research/validate_claim for fact retrieval. Even with detailed descriptions, an agent could easily misselect among data-query tools or among the five Polymarket analysis tools.

Naming Consistency3/5

Tool names mix verb-first (ask_pipeworx, compare_entities), noun-first (polymarket_edges, entity_profile), and single-word verbs (geocode, forget), with no strict verb_noun pattern. However, all names are snake_case and mostly descriptive, so the inconsistency is moderate.

Tool Count2/5

36 tools is far beyond the typical well-scoped range of 3-15, and the feature set spans research, memory, subscriptions, prediction markets, and geo utilities. Many tools are meta-tools (discover_tools, suggest_questions) that could be consolidated, making the surface feel bloated.

Completeness4/5

For the apparently broad domain of data research and prediction markets, the toolset covers most needs with parallel research, grounding, claim verification, memory, and subscription lifecycle. Minor gaps exist—like a direct way to fetch arbitrary raw data or a unified list of all tools—but agents can generally work around them.

Resources