Skip to main content
Glama

timezone-toolkit

by com.agishub

date_math

Timezone-aware date arithmetic: add or subtract a duration to a datetime (days are calendar-based and DST-safe; hours and minutes are absolute), or compute the difference between two datetimes that may be in different zones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetimeYesBase datetime: ISO 8601 or natural language.
timezoneYesIANA timezone the base datetime is in.
operationYesWhat to compute: { type:'add', amount, unit } to add/subtract a duration, or { type:'diff', to_datetime, to_timezone? } for the difference between two datetimes.

TDQS

A3.5/5.0
Behavior4/5

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

In the absence of annotations, the description adds value by disclosing behavioral traits: days are calendar-based and DST-safe, hours and minutes are absolute. This helps the agent understand edge cases, though authorization and rate limits are not mentioned.

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 description is a single sentence that efficiently conveys key points: timezone awareness, two operations, and subtle behavior (DST safety). It is concise and front-loaded with the main purpose, though slightly dense.

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?

The description covers the two operations and DST handling, but without an output schema, it fails to mention the return format or type. For a complex tool with nested parameters, this omission reduces completeness.

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%, so baseline is 3. The description adds meaning by explaining that days are DST-safe and absolute for hours/minutes. This goes beyond the schema's property descriptions, which only list types and enums.

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 tool does timezone-aware date arithmetic with two operations: add/subtract duration and compute difference. It is specific about verb and resource but does not explicitly distinguish from sibling tools like convert_timezone or now_in, though the purpose is clear.

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?

No guidance is provided on when to use this tool versus alternatives such as convert_timezone, now_in, or list_timezones. The description only states capabilities without contextual usage advice.

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

All timezone-toolkit 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

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: conversion (single and batch), arithmetic, meeting scheduling, holiday checking, timezone lookup, current time, and offset. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., convert_batch, list_timezones, is_holiday). Minor variations like 'now_in' and 'tz_offset' still adhere to the pattern.

Tool Count5/5

Nine tools is ideal for a timezone toolkit. Each tool serves a distinct and necessary function without being excessive or insufficient for the domain's scope.

Completeness5/5

The toolset covers all major timezone operations: conversion, arithmetic, current time, offset, discovery, holidays, and meeting slot calculation. No obvious gaps for common use cases.

Resources