weltze.it Zeitzonen

Uhrzeit eines Ortes

get_time

Current local time, UTC offset, DST status and the next clock change for a place or time zone. Uses the latest IANA tz data (more current than most runtimes). Accepts city names in German or English, time zone names ("Central Time", "MEZ") or IANA IDs.

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": {
      "zone": "<zone>"
    },
    "name": "get_time"
  }
}

Input Schema

Name	Required	Description	Default
`at`	No	Optional ISO 8601 instant with offset, e.g. "2026-12-01T12:00:00Z". Default: now.
`zone`	Yes	Place, time zone name or IANA ID, e.g. "San Diego", "Central Time", "Europe/Berlin".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose that this is a read-only lookup that returns time, offset, DST status and the next clock change. It also surfaces a meaningful behavioral trait: the tz database is fresher than typical runtime data, which explains reliability. It stops short of stating behavior for ambiguous or unresolvable place names.

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?

Two sentences, front-loaded with the returned data and then the input flexibility. Every clause carries information: no filler, no repetition of the tool name, and the value proposition (fresh IANA data) is compactly stated.

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 two-parameter lookup with no output schema and no annotations, the description covers what comes back, what kinds of zone strings are accepted, and the data source. The remaining gap is edge-case behavior (ambiguous city names, unknown zones) and confirmation that `at` enables non-current lookups, which the description leaves entirely to the schema.

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 both `zone` and `at` are already documented with examples, which sets the baseline at 3. The description adds a small amount beyond the schema, notably that city names are accepted in German or English (the schema only shows English examples), but it adds nothing about the `at` parameter or what an invalid instant does.

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 names both the resource (local time at a place or time zone) and the full set of returned facts: local time, UTC offset, DST status and next clock change. That is specific enough for an agent to distinguish it from `time_difference` or `convert_time`, though it never names those siblings or states what makes it different from them.

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 implied by 'for a place or time zone', and the note that it uses current IANA data 'more current than most runtimes' hints at why to prefer it, but that comparison is against runtimes rather than against the sibling tools. There is no explicit when-to-use or when-not-to-use statement and no routing to `convert_time` for conversions.

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

All weltze.it Zeitzonen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?