Skip to main content
Glama

link_datetime

Read-only

Löst eine Zeit-Nennung in einen absoluten ISO-8601-Zeitpunkt auf — „morgen früh", „heute Abend um 18 Uhr", „in zwei Stunden", „um 8:30". Auch „jetzt"/„now"/„aktuell" wird aufgelöst: nutze das als kanonische Quelle für die aktuelle Zeit, statt dir selbst ein Datum auszudenken. Das Ergebnis (candidates[].datetime_range.start) geht direkt als connections.time bzw. departures.time weiter. Nennt der Nutzer bereits eine vollständige ISO-8601-Zeit mit Offset, ist kein Aufruf nötig. Pflicht: text — die Nennung, so wie der Nutzer sie schrieb. Optional: lang ('de' Default oder 'en') und tz (IANA-Name; ohne ihn wird die Lokalzeit als Europe/Berlin gelesen und als korrekter UTC-Instant zurückgegeben); andere Werte sind ein Argument-Fehler. Was zurückkommt: EIN Zeitpunkt, kein Fenster — start und end sind derselbe Instant. Eine nicht auflösbare Phrase liefert candidates: []; dann nachfragen, statt selbst zu rechnen. Anleitung: get_usage_guide mit tool='link_datetime' — insbesondere, auf welche Stunde eine vage Tageszeit fällt und was dann zu tun ist. Anti-Fab: Datum und Uhrzeit sind Fakten wie eine Liniennummer und stammen aus diesem Werkzeug — kein selbst-erfundenes Datum, keine eigene Datums-Arithmetik. Returns candidates[].datetime_range:{start,end}.

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": {
      "text": "<text>"
    },
    "name": "link_datetime"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoOptional IANA timezone the stated local time is interpreted in (default `Europe/Berlin`). DST-aware. Pass e.g. `"Europe/Berlin"`; omit for the default. Determines the UTC instant emitted for a wall-clock mention ("8:30" → `06:30Z` in summer). A name the tz database does not know is an argument error.
langNoOptional ISO language code (default `de`): `de` or `en`, also with a region (`en-GB`). Another language is an argument error.
textYesFree-text time mention to resolve via the rustling NLU. E.g. "morgen früh", "heute Abend um 18 Uhr", "in zwei Stunden".
formatNoAnswer serialisation: `"toon"` (default) or `"json"` — the detail is in `get_usage_guide`. **An agent leaves this out.**

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Optional ISO language code (default `de`). Supported: `de`, `en`, `fr`."New value: +"Optional ISO language code (default `de`): `de` or `en`, also with a region (`en-GB`).\nAnother language is an argument error."
    • changedInput schema / properties / tz / description
      Previous value: -"Optional IANA timezone the stated local time is\ninterpreted in (default `Europe/Berlin`). DST-aware. Pass e.g.\n`\"Europe/Berlin\"`; omit for the default. Determines the UTC instant\nemitted for a wall-clock mention (\"8:30\" → `06:30Z` in summer)."New value: +"Optional IANA timezone the stated local time is\ninterpreted in (default `Europe/Berlin`). DST-aware. Pass e.g.\n`\"Europe/Berlin\"`; omit for the default. Determines the UTC instant\nemitted for a wall-clock mention (\"8:30\" → `06:30Z` in summer). A name\nthe tz database does not know is an argument error."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses the key behaviors: the result is a single instant (start equals end), nothing is returned for unresolvable phrases, and other `tz`/`lang` values constitute an argument error. It also sets an explicit anti-fabrication rule. It stops short of describing latency, ambiguity handling for multiple candidate parses, or why `candidates` is plural when only one instant is returned.

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?

It is front-loaded with the purpose and examples, then moves through parameters, return shape, and guidance in a scannable bold-labelled order. It is somewhat long for a single-parameter resolver, and the trailing 'Returns candidates[].datetime_range:{start,end}' repeats information already given in the 'Was zurückkommt' block.

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?

With no output schema, the description carries the return contract itself and does so precisely: one instant in `candidates[].datetime_range`, empty array on failure, and onward use as `connections.time`/`departures.time`. Defaults, error cases, and the follow-up path are all covered, leaving no gap for an agent calling this tool.

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 the schema already documents all four parameters including the Berlin default and the DST conversion. The description restates the required `text` and the optional `lang`/`tz` with their defaults and error conditions, which is useful reinforcement but adds little meaning beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: resolving a time mention into an absolute ISO-8601 instant, illustrated with four concrete example phrases. It further states that it is the canonical source for the current time, which is a distinct capability no sibling travel tool provides.

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

Usage Guidelines5/5

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

It gives both sides of the routing decision: call it for vague mentions like 'morgen früh' or for 'jetzt'/'now', but do not call it when the user already supplied a complete ISO-8601 time with offset. It also names `get_usage_guide` with the exact tool value for deeper questions and prescribes follow-up questioning when `candidates` is empty.

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