Skip to main content
Glama

timezone

by io.github.pipeworx-io

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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
to_datetimeYesConverted datetime in ISO 8601 format
to_timezoneYesTarget timezone
from_datetimeYesSource datetime in ISO 8601 format
from_timezoneYesSource timezone
to_utc_offsetYesUTC offset of target timezone in ±HH:MM format
from_utc_offsetYesUTC offset of source timezone in ±HH:MM format
offset_differenceYesDifference in UTC offsets in ±HH:MM format

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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)."
  2. Added
  3. Removed
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds the default current-time behavior, which is a useful behavioral trait beyond the annotation metadata. No contradictions with annotations.

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?

Two short sentences, front-loaded with the primary action, no redundant information. Every word contributes to clarifying purpose or usage.

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

Completeness5/5

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

For a simple conversion tool with a full input schema, output schema, and annotations, the description covers the essential purpose and the one non-obvious behavior (default time). No significant gaps remain.

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%, but the description adds semantic context for the optional 'time' parameter, explaining that omitting it defaults to current time in the source timezone. This enhances understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses a specific verb ('convert') and resource ('datetime from one timezone to another'), clearly distinguishing from sibling tools like list_timezones or get_time_by_timezone. The action and scope are unambiguous.

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 description provides clear context for when to use this tool (converting between timezones) and specifies the behavior when 'time' is omitted. It does not explicitly name alternative tools, but the intended use is unambiguous and no exclusions are needed.

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

All timezone toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the multiple 'ask_pipeworx' variants and several Polymarket utilities. The server mixes a few timezone tools with a large collection of unrelated data lookup and analysis tools, making it hard for an agent to distinguish which tool to use for a given task.

Naming Consistency2/5

While all tool names use snake_case, the verbs are highly inconsistent (e.g., 'ask_pipeworx', 'convert_time', 'discover_tools', 'validate_claim'). There is no clear pattern or predictable naming convention across the set.

Tool Count2/5

The server name 'timezone' suggests a narrow domain, but it contains 35 tools, the vast majority of which are unrelated to timezones. This is far too many for the implied scope, and the server seems to be a dumping ground for various services.

Completeness1/5

For a timezone server, only 4 tools (convert_time, get_time_by_ip, get_time_by_timezone, list_timezones) are relevant. Critical timezone functionality like time zone conversions with arbitrary offsets, DST handling, or time zone by coordinates is missing. The remaining tools are completely unrelated to the server's stated purpose.

Resources