Skip to main content
Glama
Sign In
Time MCP Server

Time MCP Server

by hypnwtykvmpr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

convert_time

Read-onlyIdempotent

Convert a 24-hour time from one IANA timezone to another by specifying source and target timezones, so you can schedule across regions.

Instructions

Convert time between timezones

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>"
    },
    "name": "convert_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesTime to convert in 24-hour format (HH:MM)
source_timezoneNoSource IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Optional: defaults to the server's local timezone, 'Etc/UTC', when omitted.Etc/UTC
target_timezoneNoTarget IANA timezone name (e.g., 'Asia/Tokyo', 'America/San_Francisco'). Optional: defaults to the server's local timezone, 'Etc/UTC', when omitted.Etc/UTC

Output Schema

NameRequiredDescriptionDefault
sourceYes
targetYes
time_differenceYes
later_occurrenceNoSet only when the source time occurs twice on this date because a clock change repeats it (a DST fall-back): the same conversion at its second occurrence. source and target are the first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.11

TDQS

C2.9/5.0
Behavior2/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 the safety profile is fully covered. The description adds nothing beyond that: it does not say how defaults are resolved, whether the conversion accounts for DST, or what happens when an invalid timezone is given. With annotations doing all the work, the description contributes little extra context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words, but it is under-specified rather than concise: the terseness leaves out useful details about defaults and output. There is nothing to front-load, because there is only one clause.

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 not be explained, and the schema fully documents the three parameters. However, for a tool whose core behavior depends on timezone defaults and DST handling, the description leaves those semantics entirely to the schema and annotations. It is minimally sufficient but not complete.

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%, and each parameter is documented in the schema, including the HH:MM format and the Etc/UTC default behavior. The description adds no meaning beyond the schema, which is acceptable at the baseline of 3.

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: convert, time, between timezones. It is unambiguous and clearly distinct from the sibling tools get_current_time and get_time_ago. It stops short of a 5 because it does not explicitly contrast itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of the alternative tools. An agent can infer that this tool converts an existing time value while get_current_time reads the clock, but the definition itself supplies no routing logic or preconditions.

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