Skip to main content
Glama

timezone

by io.github.pipeworx-io

Get Time By Timezone

get_time_by_timezone
Read-onlyIdempotent

Get the current date and time in a specific IANA timezone (e.g. "America/New_York", "Europe/London", "Asia/Tokyo").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneYesIANA timezone string, e.g. "America/New_York"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetimeYesISO 8601 datetime in the requested timezone
timezoneYesIANA timezone name
utc_offsetYesUTC offset in ±HH:MM format
day_of_weekYesDay of week (0-6)
day_of_yearYesDay of year (1-366)
week_numberYesWeek number of the year

Schema Changelog

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

  1. Added
  2. Removed
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is known. The description adds no further behavioral details beyond stating it returns the current date and time, which is consistent with the 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?

The description is a single, focused sentence with no redundant information. It conveys the tool's purpose efficiently.

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?

Given the tool's simplicity—one parameter, a read-only operation, and an output schema presumably documenting return values—the description is sufficiently complete. It covers the purpose and parameter format without unnecessary elaboration.

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?

The input schema fully documents the timezone parameter with type and description. The description adds value by giving concrete examples of IANA timezone formats (America/New_York, Europe/London, Asia/Tokyo), which aids correct invocation.

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 clearly states the verb 'get' and the resource 'current date and time in a specific IANA timezone'. It is unambiguous and distinguishes the tool's core function, but it does not explicitly differentiate it from sibling tools like get_time_by_ip or convert_time.

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?

The description provides no guidance on when to use this tool versus alternatives. Sibling tools such as get_time_by_ip and convert_time exist, but the description neither mentions them nor excludes any scenarios. Usage is only implied by the description.

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