Skip to main content
Glama

Convert a time between timezones

convert_time
Read-onlyIdempotent

Convert an ISO 8601 / RFC 3339 date-time to another IANA timezone, handling daylight saving 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": {
      "datetime": "<datetime>"
    },
    "name": "convert_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
datetimeYesDate-time, e.g. 2026-03-29T01:30:00Z, or without offset with from_timezone.
to_timezoneNoIANA timezone name, e.g. Europe/Paris or America/New_York. Default UTC.
from_timezoneNoIANA timezone of a date-time without offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / datetime / description
      Previous value: -"e.g. 2026-03-29T01:30:00Z or 2026-03-29T01:30:00"New value: +"Date-time, e.g. 2026-03-29T01:30:00Z, or without offset with from_timezone."
    • changedInput schema / properties / from_timezone / description
      Previous value: -"IANA timezone of a datetime without offset"New value: +"IANA timezone of a date-time without offset."
    • changedInput schema / properties / to_timezone / description
      Previous value: -"Target IANA timezone, default UTC"New value: +"IANA timezone name, e.g. Europe/Paris or America/New_York. Default UTC."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and purity are covered. The description adds real value with 'handling daylight saving time', but it says nothing about error behavior for invalid IANA names or ambiguous/nonexistent local times during DST transitions.

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?

A single front-loaded sentence with the core action first and the DST caveat second. No filler, no redundancy with the title.

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

Completeness3/5

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

With three fully documented parameters and rich annotations, most of the call is covered. However, there is no output schema, and the description never states what is returned (e.g., a formatted string in the target zone, or whether the offset is included), leaving the response shape to inference.

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 schema already documents all three parameters including the from_timezone/to_timezone relationship. The description adds only the DST-handling note and no additional syntax or constraint detail, so baseline 3 applies.

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 gives a specific verb and resource: converting an ISO 8601 / RFC 3339 date-time into an IANA timezone. That is clearly distinct from siblings like get_current_time or compute_duration without needing to name them, though it does not explicitly contrast with any alternative.

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 implied by the phrasing — use this when you have a timestamp and need it expressed in another zone. There is no explicit when-to-use/when-not guidance and no mention of which sibling to prefer for adjacent tasks such as getting the current time.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.