Skip to main content
Glama

Blackwood State

by io.github.Blackwood-State
OverviewDiscussionsAdmin

Time zones

blackwood_timezone_convert
Read-onlyIdempotent

Use when you need timezone conversion between time zones, the current time in a zone or a utc offset with daylight saving. Do not use for places given only by city or address without an IANA zone name, or dates before 1970. Returns JSON converting a date and time between IANA time zones with daylight saving rules, with UTC offsets, abbreviations and the current time in each zone, from the IANA tz database for 0.003 USDC per call. Typical response time 500 ms (p95). Category: Data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesIANA time zones to convert to, e.g. ["Europe/London", "Asia/Tokyo"]
fromNoIANA time zone of a local time, e.g. America/Sao_Paulo (UTC when omitted)
timeNoDate and time to convert, ISO 8601: local wall time like 2026-10-17T15:30 (read in the from zone) or an instant with Z or an offset; now when omitted
response_formatNoconcise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "epochMs": {
-        "type": "number"
-      },
-      "from": {
-        "additionalProperties": false,
-        "properties": {
-          "abbreviation": {
-            "type": "string"
-          },
-          "dst": {
-            "type": "boolean"
-          },
-          "localTime": {
-            "type": "string"
-          },
-          "offset": {
-            "type": "string"
-          },
-          "offsetMinutes": {
-            "type": "number"
-          },
-          "zone": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "zone",
-          "localTime",
-          "offset",
-          "offsetMinutes",
-          "abbreviation",
-          "dst"
-        ],
-        "type": "object"
-      },
-      "instant": {
-        "type": "string"
-      },
-      "source": {
-        "type": "string"
-      },
-      "to": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "abbreviation": {
-              "type": "string"
-            },
-            "dst": {
-              "type": "boolean"
-            },
-            "localTime": {
-              "type": "string"
-            },
-            "offset": {
-              "type": "string"
-            },
-            "offsetMinutes": {
-              "type": "number"
-            },
-            "zone": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "zone",
-            "localTime",
-            "offset",
-            "offsetMinutes",
-            "abbreviation",
-            "dst"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "instant",
-      "epochMs",
-      "from",
-      "to",
-      "source"
-    ],
-    "type": "object"
-  },
-  {
-    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
-    "properties": {
-      "accepts": {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "error": {
-        "type": "string"
-      },
-      "extensions": {
-        "type": "object"
-      },
-      "resource": {
-        "type": "object"
-      },
-      "x402Version": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "x402Version",
-      "accepts"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "epochMs": {
+        "type": "number"
+      },
+      "from": {
+        "additionalProperties": false,
+        "properties": {
+          "abbreviation": {
+            "type": "string"
+          },
+          "dst": {
+            "type": "boolean"
+          },
+          "localTime": {
+            "type": "string"
+          },
+          "offset": {
+            "type": "string"
+          },
+          "offsetMinutes": {
+            "type": "number"
+          },
+          "zone": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "zone",
+          "localTime",
+          "offset",
+          "offsetMinutes",
+          "abbreviation",
+          "dst"
+        ],
+        "type": "object"
+      },
+      "instant": {
+        "type": "string"
+      },
+      "next": {
+        "additionalProperties": false,
+        "description": "Suggested next paid call in the same family (call it in a loop when the task continues)",
+        "properties": {
+          "method": {
+            "enum": [
+              "GET",
+              "POST"
+            ],
+            "type": "string"
+          },
+          "sample": {
+            "description": "Free fixed sample of the whole family",
+            "type": "string"
+          },
+          "service": {
+            "description": "Service id of the suggested next paid call",
+            "type": "string"
+          },
+          "tool": {
+            "description": "MCP tool name of the same call",
+            "type": "string"
+          },
+          "url": {
+            "description": "Paid route of the next call",
+            "type": "string"
+          },
+          "useWhen": {
+            "description": "When the next call is the right one",
+            "type": "string"
+          }
+        },
+        "required": [
+          "service",
+          "tool",
+          "method",
+          "url",
+          "useWhen",
+          "sample"
+        ],
+        "type": "object"
+      },
+      "source": {
+        "type": "string"
+      },
+      "to": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "abbreviation": {
+              "type": "string"
+            },
+            "dst": {
+              "type": "boolean"
+            },
+            "localTime": {
+              "type": "string"
+            },
+            "offset": {
+              "type": "string"
+            },
+            "offsetMinutes": {
+              "type": "number"
+            },
+            "zone": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "zone",
+            "localTime",
+            "offset",
+            "offsetMinutes",
+            "abbreviation",
+            "dst"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "instant",
+      "epochMs",
+      "from",
+      "to",
+      "source"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "x402 PaymentRequired (returned with isError when payment is needed)",
+    "properties": {
+      "accepts": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      },
+      "extensions": {
+        "type": "object"
+      },
+      "resource": {
+        "type": "object"
+      },
+      "x402Version": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "x402Version",
+      "accepts"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on genuinely new operational context: per-call cost (0.003 USDC), p95 latency (500 ms), the backing data source (IANA tz database), and the exact shape of the returned JSON. None of this is derivable from the structured fields.

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?

Front-loaded with the use/when-not framing before any details, which is the right ordering. Nearly every clause earns its place, though the trailing 'Category: Data' is filler and the pricing/latency could be read as marginally optional.

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?

Output schema exists so return values need not be spelled out, yet the description still previews them (offsets, abbreviations, current time per zone). Combined with cost, latency, data source, and explicit exclusions, an agent has everything needed to select and call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description still adds value by constraining valid inputs (IANA zone names only, no city/address resolution, 1970 lower bound) and by clarifying that `to` is plural while `from` is singular. It does not restate ISO 8601 mechanics, which the schema already covers.

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?

States a specific verb+resource (timezone conversion), and enumerates the exact sub-capabilities it covers: conversion between zones, current time in a zone, and UTC offsets with daylight saving. An agent can immediately tell this apart from data-oriented siblings like fx_rates or weather_forecast.

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?

Explicit 'Use when...' clause followed by explicit exclusions ('Do not use for places given only by city or address without an IANA zone name, or dates before 1970'). The boundary conditions that would cause a wrong invocation are named directly.

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

All Blackwood State toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources