weltze.it Zeitzonen

Uhrzeit umrechnen

convert_time

Convert a local wall-clock time in one place to another place. Reports nonexistent (DST gap) and ambiguous (DST overlap) times.

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

Input Schema

Name	Required	Description
`to`	Yes	Target place or zone.
`from`	Yes	Place or zone of the given time.
`time`	Yes	Local time without offset in the "from" place, "YYYY-MM-DDTHH:MM", e.g. "2026-12-01T13:30".
`disambiguation`	No	Which instant to use for an ambiguous time. Default earlier.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.6/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, and it does disclose one genuinely useful behavior beyond the schema: it surfaces DST gaps and overlaps. However, it does not say what actually happens for a nonexistent time (error, rejection, or silent shift), nor does it describe the return value, which matters for a conversion tool with no output schema.

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?

Two short sentences, front-loaded with the core action and followed by the edge-case behavior. No filler or redundancy, though the DST clause could have been tied more explicitly to the disambiguation parameter.

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 four-parameter conversion tool with a fully documented schema, the definition covers the action, the input format expectation, and the DST edge cases an agent must anticipate. With no output schema, the lack of return-value detail is a minor gap rather than a blocking omission.

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%, including the format example for 'time' and the disambiguation enum, so the schema already documents all four parameters. The description adds no additional meaning about parameter interaction or interpretation, making the baseline 3 appropriate.

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 local wall-clock time from one place to another. The emphasis on 'local wall-clock time' separates it from a raw epoch/instant conversion, but it never names or contrasts the sibling tools get_time or time_difference, so differentiation is left to inference.

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 the phrase 'local wall-clock time in one place to another place,' which suggests this is the tool for cross-zone conversion rather than elapsed-time math. There is no explicit when-to-use statement, no mention of when to prefer time_difference or get_time, and no stated prerequisites.

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?