Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_geo_timezone_converter

Convert a date-time between IANA timezones and return offsets, abbreviations, and DST flags so you can schedule or log events accurately across regions.

Instructions

[Global Locale] Convert a date-time between IANA timezones with offsets, abbreviations and DST flags Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://geo.caelaralabs.com.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "caelara_geo_timezone_converter"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesComma list of target IANA timezones
fromYesSource IANA timezone, e.g. America/New_York
timeNoISO 8601 time; wall time is read in the source timezone (default now)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses latency benchmarks and the backing endpoint, but says nothing about authentication, error handling on invalid timezone strings, or the actual response shape beyond three named fields.

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 short and front-loaded with purpose, but the second sentence is a run-on with a missing separator ("DST flags Measured p50"), and the raw endpoint URL and benchmark citation are low-value for an agent deciding how to call the tool.

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

Completeness4/5

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

For a simple three-parameter converter with full schema coverage, the description covers purpose and names the returned fields, which compensates for the absent output schema. Residual gaps are operational (auth, error behavior) rather than blocking.

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 all three parameters are already documented, including that wall time is read in the source timezone and defaults to now. The description adds no format or validation detail beyond the schema, so the baseline 3 applies.

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 a date-time between IANA timezones", and it names the output dimensions (offsets, abbreviations, DST flags). It does not explicitly distinguish itself from conversion-adjacent siblings like global_scheduling_composite or business_hours_calc, so it stops short of a 5.

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

Usage Guidelines3/5

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

The verb "Convert" implies the use case, so an agent can infer this is the tool for shifting a timestamp across zones. However, there is no explicit when-to-use/when-not guidance and no mention of the sibling composite tools that also touch timezones, leaving routing to inference.

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