Skip to main content
Glama

Caelara Labs Global Locale

timezone_converter

Convert a date-time between IANA timezones with offsets, abbreviations and DST flags

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": "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 observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the result includes offsets, abbreviations and DST flags, which partially compensates for the absent output schema, but it says nothing about error behavior for invalid IANA identifiers, ambiguous/nonexistent DST wall times, or limits on the number of target timezones.

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?

A single dense sentence with the core action front-loaded and no filler. It is efficient, though the trailing 'with offsets, abbreviations and DST flags' mixes return-value information into the purpose statement without labeling it as such.

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, fully documented conversion tool with no output schema, the description covers the operation and sketches the return fields. The main residual gap is DST edge-case behavior, which matters for a timezone tool but is a modest omission given the schema already handles defaults and formats.

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 `time` defaults to now and is read as wall time in the source timezone. The description adds no additional semantics about the parameters (e.g. how multiple comma-separated targets are handled), 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?

States a specific verb and resource: convert a date-time between IANA timezones. The mention of offsets, abbreviations and DST flags further narrows the scope, making it clearly distinct from calculation-oriented siblings like business_hours_calc or distance_haversine_calc, though no sibling is named explicitly.

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?

Usage is only implied by the name and the phrase 'Convert a date-time between IANA timezones' — an agent can infer this is for timezone conversion. There is no explicit when-to-use versus when-not, no mention of the composite or scheduling siblings, and no prerequisites stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources