Skip to main content
Glama
Sign In

Time of Meeting

by com.timeofmeeting
OverviewDiscussionsAdmin

Daylight-saving changes

get_dst_changes
Read-onlyIdempotent

List daylight saving time (DST) clock changes for one city. Use when the user asks when the clocks change, or whether a recurring meeting moves when DST starts or ends. Defaults to the next year. Each change includes the local time and the ISO week and US week of that local date. The range can be at most 366 days.

Input Schema

NameRequiredDescriptionDefault
cityYesCity name or a city id from a city search. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives.
end_dateNoLast day, YYYY-MM-DD. Defaults to 365 days later.
start_dateNoFirst day, YYYY-MM-DD. Defaults to today (UTC).

Output Schema

NameRequiredDescriptionDefault
cityYes
errorNo
changesYes
end_dateYes
candidatesNo
start_dateYes
alternativesNoOther cities that matched the same name, after the best-ranked city was chosen. The order is the site search order: match, then priority, then population.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"City name or a city id from search_cities. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives."New value: +"City name or a city id from a city search. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives."
  2. Changed5 schema fields changed
    • removedOutput schema / properties / changes / items / properties / link
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / changes / items / properties / weeks
      Added value: +{
+  "additionalProperties": false,
+  "description": "ISO week (Monday start; week 1 contains the year's first Thursday) and US week (Sunday start; 1 January is week 1 of that calendar year).",
+  "properties": {
+    "iso_week": {
+      "maximum": 53,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "us_week": {
+      "maximum": 54,
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "iso_week",
+    "us_week"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / changes / items / required
      Previous value: -[
-  "at",
-  "local",
-  "before",
-  "after",
-  "direction",
-  "reason",
-  "link"
-]New value: +[
+  "at",
+  "local",
+  "weeks",
+  "before",
+  "after",
+  "direction",
+  "reason"
+]
    • removedOutput schema / properties / link
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "link",
-  "city",
-  "start_date",
-  "end_date",
-  "changes"
-]New value: +[
+  "city",
+  "start_date",
+  "end_date",
+  "changes"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"City name or a city id from search_cities. Spelling and accents are flexible."New value: +"City name or a city id from search_cities. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives."
    • addedOutput schema / properties / alternatives
      Added value: +{
+  "description": "Other cities that matched the same name, after the best-ranked city was chosen. The order is the site search order: match, then priority, then population.",
+  "items": {
+    "properties": {
+      "country": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": "string"
+      },
+      "region": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's job is to add operational context — and it does: default range of the next year, the 366-day range cap, and the presence of local time plus ISO and US week fields per change. It adds no return format details beyond that, which is acceptable given the output schema exists.

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?

Four tight sentences, front-loaded with the core action, then usage triggers, defaults, and the range constraint. Every sentence carries information an agent needs; nothing is padded.

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 read-only lookup with full schema coverage and an output schema, the description covers purpose, triggers, defaults, and the range limit. The one gap is disambiguation from dst_check, which would make an agent fully confident in tool selection.

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 description coverage is 100%, so the schema already documents city matching, fuzzy spelling, alternatives, and the date formats. The description only restates the date-range default and the 366-day limit, adding little beyond the structured fields — baseline 3 is 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?

"List daylight saving time (DST) clock changes for one city" states a specific verb and resource with an explicit scope of one city. It is clear what the tool returns, though it does not explicitly contrast with the sibling dst_check, which an agent could plausibly confuse it with.

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

Usage Guidelines4/5

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

It gives clear when-to-use triggers: "when the user asks when the clocks change, or whether a recurring meeting moves when DST starts or ends." No alternative is named (dst_check is the obvious adjacent tool), so it stops just short of full routing guidance.

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

All Time of Meeting toolsInspect
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