Skip to main content
Glama

Convert Time

convert_time
Read-onlyIdempotent

Convert a datetime from one timezone to another. If no time is provided the current time in the source timezone is used.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to_timezone": "Europe/London",
      "from_timezone": "America/New_York"
    },
    "name": "convert_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoDatetime to convert as "YYYY-MM-DD HH:mm:ss" (optional, defaults to current time in source).
to_timezoneYesTarget IANA timezone, e.g. "Europe/Paris"
from_timezoneYesSource IANA timezone, e.g. "America/New_York"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / time / description
      Previous value: -"Datetime to convert as \"YYYY-MM-DD HH:mm:ss\" (optional — defaults to current time in source)."New value: +"Datetime to convert as \"YYYY-MM-DD HH:mm:ss\" (optional, defaults to current time in source)."
  2. Changed3 schema fields changed
    • addedOutput schema / oneOf
      Added value: +[
      +  {
      +    "properties": {
      +      "found": {
      +        "description": "Present and true on an answer; a miss is the found:false branch.",
      +        "enum": [
      +          true
      +        ],
      +        "type": "boolean"
      +      },
      +      "from_datetime": {
      +        "description": "Source datetime in ISO 8601 format",
      +        "type": "string"
      +      },
      +      "from_timezone": {
      +        "description": "Source timezone",
      +        "type": "string"
      +      },
      +      "from_utc_offset": {
      +        "description": "UTC offset of source timezone in ±HH:MM format",
      +        "type": "string"
      +      },
      +      "offset_difference": {
      +        "description": "Difference in UTC offsets in ±HH:MM format",
      +        "type": "string"
      +      },
      +      "to_datetime": {
      +        "description": "Converted datetime in ISO 8601 format",
      +        "type": "string"
      +      },
      +      "to_is_dst": {
      +        "type": "boolean"
      +      },
      +      "to_timezone": {
      +        "description": "Target timezone",
      +        "type": "string"
      +      },
      +      "to_utc_offset": {
      +        "description": "UTC offset of target timezone in ±HH:MM format",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "from_timezone",
      +      "from_datetime",
      +      "to_timezone",
      +      "to_datetime"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "description": "A miss or an unavailable upstream: found:false with a reason and a hint (the shape check-found-false-schemas.mjs expects).",
      +    "properties": {
      +      "found": {
      +        "enum": [
      +          false
      +        ],
      +        "type": "boolean"
      +      }
      +    },
      +    "required": [
      +      "found"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "from_datetime": {
      -    "description": "Source datetime in ISO 8601 format",
      -    "type": "string"
      -  },
      -  "from_timezone": {
      -    "description": "Source timezone",
      -    "type": "string"
      -  },
      -  "from_utc_offset": {
      -    "description": "UTC offset of source timezone in ±HH:MM format",
      -    "type": "string"
      -  },
      -  "offset_difference": {
      -    "description": "Difference in UTC offsets in ±HH:MM format",
      -    "type": "string"
      -  },
      -  "to_datetime": {
      -    "description": "Converted datetime in ISO 8601 format",
      -    "type": "string"
      -  },
      -  "to_is_dst": {
      -    "type": "boolean"
      -  },
      -  "to_timezone": {
      -    "description": "Target timezone",
      -    "type": "string"
      -  },
      -  "to_utc_offset": {
      -    "description": "UTC offset of target timezone in ±HH:MM format",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "from_timezone",
      -  "from_datetime",
      -  "to_timezone",
      -  "to_datetime"
      -]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / to_is_dst
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "from_timezone",
      -  "from_datetime",
      -  "from_utc_offset",
      -  "to_timezone",
      -  "to_datetime",
      -  "to_utc_offset",
      -  "offset_difference"
      -]New value: +[
      +  "from_timezone",
      +  "from_datetime",
      +  "to_timezone",
      +  "to_datetime"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / time / description
      Previous value: -"ISO 8601 datetime to convert (optional — defaults to now). E.g. \"2024-06-15T14:30:00\""New value: +"Datetime to convert as \"YYYY-MM-DD HH:mm:ss\" (optional — defaults to current time in source)."
  5. Added
  6. Removed
  7. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description's only added behavioral detail is the fallback to current time when 'time' is omitted, which is also stated in the schema. It adds a small amount of context but nothing beyond what annotations plus schema already convey.

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?

Two short sentences with no filler, and the core purpose is front-loaded before the fallback detail. There is no wasted text, though it is minimal to the point of omitting anything an agent couldn't already read from structured fields.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover the safety and idempotency profile. With 100% parameter coverage in the schema, the description only needs to frame the operation, which it does. Minor gap: no note on how ambiguous or DST-affected local times are handled.

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 (time format, source IANA zone, target IANA zone) are documented with examples in the schema itself. The description restates the optional-time default without adding format, range, or edge-case semantics (e.g., DST handling). Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Convert a datetime from one timezone to another.' An agent can immediately tell this transforms a supplied datetime, as opposed to siblings like get_time_by_timezone or get_time_by_ip that appear to fetch current time. It doesn't explicitly name those siblings, so it falls short of the 5 bar.

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 conversion framing and the note that omitting time uses the current time in the source zone, which quietly signals 'use this when you have a target timezone pair.' However, there is no explicit when-to-use or when-not guidance, no mention of how this differs from get_time_by_timezone or list_timezones, and no prerequisites stated.

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.