Skip to main content
Glama
World Time MCP Server

World Time MCP Server

convert_time

Read-only

Convert a time from one city to another to see the local time at the destination. Enter a time, source city, and target city for accurate cross-city time conversion.

Instructions

Convert a time in one city to the local time in another city.

Args: time: Time in the source city: "14:30", "2:30 PM", or "2026-03-29 14:30" / "2026-03-29 2:30 PM" for a specific date. Time-only values are taken as today in from_city. from_city: City (or IANA zone) the time belongs to. to_city: City (or IANA zone) to convert the time to.

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": {
      "time": "<time>",
      "from_city": "<from_city>",
      "to_city": "<to_city>"
    },
    "name": "convert_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYes
to_cityYes
from_cityYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=false, so the safety profile is known. The description adds genuine behavioral context beyond that — the time-only-means-today-in-from_city rule and accepted format variants — but says nothing about DST edge cases, ambiguous zone resolution, or error behavior for unparseable input.

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?

The one-line summary is front-loaded and the Args block is scannable, with each parameter given exactly one line of useful detail. The docstring 'Args:' formatting is slightly tool-internal but does not waste words.

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?

An output schema exists, so return values need no explanation, and the three required parameters are each documented. What is missing is the edge-case behavior an agent would need for correct invocation of a timezone tool: ambiguous city resolution and DST ambiguity handling.

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 0% and the bare 'Time'/'From City'/'To City' titles carry no semantics, so the description must compensate — and it does, giving accepted time formats with concrete examples ('14:30', '2026-03-29 2:30 PM'), the default-to-today rule, and clarifying that cities may also be IANA zones. It stops short of noting ambiguous city names or how DST transitions are handled.

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 states a specific verb and resource: convert a time from one city's local zone to another city's local time. It is clearly distinct from the sibling tools get_time, compare_times, and find_cities by virtue of being a conversion rather than a lookup or comparison, though it never names an alternative explicitly.

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 purpose statement and by the note that time-only values are taken as today in from_city, but there is no explicit guidance on when to choose this over compare_times or get_time, and no stated exclusions or prerequisites.

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

Deploy Server

Other Tools