Skip to main content
Glama

Agent Bits

by io.github.rwaldman

timezone_convert

Convert an ISO-8601 datetime from one IANA timezone to another while preserving the same instant, including daylight-saving-aware wall times such as Toronto to Tokyo.

Use when:

  • What time is 3pm Toronto in Tokyo?

  • Convert an ISO-8601 datetime from America/New_York to Europe/London

  • Show the same instant in another IANA timezone with DST-aware offsets

Do not use when:

  • Only convert between Unix epoch and ISO-8601 without changing timezone (use timestamp_convert)

  • Convert length, mass, or temperature units (use unit_convert)

  • Guess a city timezone from a postal address without an IANA zone id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetimeYesISO-8601 datetime, with or without offset
to_timezoneYesIANA timezone for output
from_timezoneYesIANA timezone for interpreting naive datetimes

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses core behavior: preserving the same instant, DST-aware offsets, and interpreting naive datetimes via from_timezone. It does not mention error handling or output format, but for this tool the essential behavior is well covered.

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 concise, front-loaded with the primary purpose, and uses bullet-style sections for usage guidance. No wasted sentences; every section earns its place.

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 3-parameter conversion tool with full schema coverage, the description provides complete context: purpose, examples, alternatives, and boundary conditions. No output schema is needed for this straightforward transformation.

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 coverage is 100%, so parameters are fully described in structured data. The description adds examples but does not significantly enrich parameter semantics beyond what the schema already states.

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?

The description clearly states the tool converts ISO-8601 datetimes between IANA timezones while preserving the same instant, with DST-awareness. It is distinct from siblings like timestamp_convert and unit_convert through explicit examples and exclusions.

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

Usage Guidelines5/5

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

Explicit 'Use when' and 'Do not use when' sections provide clear contextual guidance, naming specific alternatives (timestamp_convert, unit_convert) and example queries that illustrate appropriate usage.

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

All Agent Bits 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.3/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear use cases and explicit 'Do not use when' guidance preventing confusion. For example, base64_decode and url_decode handle different encoding schemes, while timestamp_convert and timezone_convert address separate time operations.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., base64_decode, country_lookup, uuid_validate). While verbs vary (decode, encode, lookup, validate, convert), the naming format is uniform and predictable.

Tool Count4/5

The 18-tool set is slightly above the typical 3-15 range, but the breadth is justified by the server's purpose as a general-purpose utility toolkit. Each tool earns its place, and the count does not feel overwhelming or redundant.

Completeness4/5

The toolkit covers encoding/decoding, validation, lookups, and conversions across common developer needs. Minor gaps exist, such as no UUID generation tool to complement uuid_validate, and no HTML entity encoding/decoding, but these are not critical omissions for the stated utility scope.

Resources