Skip to main content
Glama

convert_timezone

Read-onlyIdempotent

Convert an ISO-8601 timestamp to a target IANA timezone to get localized time, UTC offset, and a readable format. Use it to display or compare a moment in another region's local time.

Instructions

Converts an ISO-8601 timestamp to a target IANA timezone. The input timestamp must include timezone information or be in UTC. Returns the localised time, UTC offset, and human-readable format. Use when you need to display or compare a moment in another region's local time.

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": {
      "timestamp": "<timestamp>",
      "target_tz": "<target_tz>"
    },
    "name": "convert_timezone"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_tzYesTarget IANA timezone identifier.
timestampYesISO-8601 timestamp to convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: the input constraint that the timestamp must carry timezone info or be UTC, and what the result contains. Minor gaps remain around DST ambiguity or invalid timezone handling.

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?

Three short sentences, front-loaded with the operation, then the input precondition, then the return shape and usage. No filler; the phrasing is efficient, though 'human-readable format' is slightly loose terminology.

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 correctly covers the return values (localized time, UTC offset, human-readable form), and with only two fully documented parameters nothing essential is missing. Edge-case behavior such as invalid IANA identifiers or DST transitions is not addressed, keeping it below a 5.

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 adds a constraint not expressed in the schema: the timestamp must include timezone information or be in UTC. That is genuine semantic value for the timestamp parameter beyond its schema description.

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 first sentence names a specific verb and resource ('Converts an ISO-8601 timestamp to a target IANA timezone'), making the operation unmistakable. It does not explicitly differentiate itself from adjacent siblings such as time_math or get_current_time, so it falls short of a 5.

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 final sentence gives a concrete usage condition ('display or compare a moment in another region's local time'), which is clear context for invocation. It stops short of exclusions or naming an alternative tool, so no explicit when-not guidance is present.

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