weltze.it Zeitzonen

Zeitverschiebung

time_difference

Time difference between two places now, and how it changes over the coming months because of clock changes.

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": "time_difference"
  }
}

Input Schema

Name	Required	Description
`at`	No	Optional ISO 8601 instant. Default: now.
`to`	Yes	Other place or zone, e.g. "New York".
`from`	Yes	Reference place or zone, e.g. "Berlin".
`months`	No	How many months of changes to list. Default 12.

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?

No annotations are supplied, so the description must carry the burden; it does disclose that the response includes both the current difference and a forward-looking list of changes. It says nothing about output format, how place names are resolved, or error behavior for unknown places, leaving real gaps for a zero-annotation tool.

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?

A single sentence that front-loads the primary result and appends the secondary capability without filler. Nothing could be removed without losing meaning.

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 four-parameter read-only computation with full schema coverage and no output schema, the description adequately conveys what the result contains (current offset plus monthly changes). The only shortfall is that it doesn't clarify how place strings are interpreted or what the returned change list looks like.

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 four parameters (including required from/to and optional at/months) are already documented with examples and defaults. The description only echoes the 'now' default and the months horizon; it adds no syntax or resolution semantics beyond the schema.

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 computation (time difference between two places) plus a distinctive extra capability (how it shifts over coming months due to clock changes). This separates it in spirit from get_time or convert_time, though it never names a sibling to make the contrast explicit.

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 phrase 'between two places' and 'over the coming months' implies when to reach for this tool rather than a single-instant lookup, but there is no explicit when-to-use, when-not-to-use, or named alternative such as convert_time.

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?