Skip to main content
Glama
temporal-mcp-server

temporal-mcp-server

convert_timezone

Convert an ISO-8601 timestamp into wall-clock time for a target IANA timezone, using a source timezone when the input lacks an offset.

Instructions

Render an ISO-8601 timestamp as wall-clock time in a target timezone.

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": {
      "isoTimestamp": "<isoTimestamp>",
      "targetTimezone": "<targetTimezone>"
    },
    "name": "convert_timezone"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoTimestampYesISO-8601 timestamp to convert, e.g. '2026-08-17T14:30:00Z'.
sourceTimezoneNoIANA timezone used to interpret `isoTimestamp` when it carries no 'Z' or offset. Ignored otherwise. Defaults to UTC.
targetTimezoneYesIANA timezone identifier to render in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / sourceTimezone
      Added value: +{
      +  "description": "IANA timezone used to interpret `isoTimestamp` when it carries no 'Z' or offset. Ignored otherwise. Defaults to UTC.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does not say whether this is a pure non-mutating computation, how DST gaps/ambiguities are resolved, or what the returned value looks like. 'Wall-clock time' is the only hint at output shape, and it is ambiguous about whether an offset is included.

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?

It is a single front-loaded sentence with no filler or redundancy. The terseness is efficient, though it leaves real gaps that are penalized under other dimensions.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place to learn the return format, DST behavior, and error conditions, and it covers none of these. For a conversion tool with a conditional optional parameter, this is under-specified.

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 all three parameters, including the conditional sourceTimezone behavior, are already fully documented in the schema. The description adds no further meaning about parameter interaction or constraints, which is the expected baseline when the schema does the work.

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 states a specific verb and resource: 'Render an ISO-8601 timestamp as wall-clock time in a target timezone.' That is enough to distinguish it from siblings such as add_duration and get_current_time, but it never names an alternative or explicitly contrasts its role.

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. An agent can infer this is the tool for expressing a known timestamp in another zone while add_duration and time_between handle arithmetic, but there is no explicit when-to-use, when-not-to-use, or alternative named.

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