Time of Meeting

Convert a local time

convert_time

Read-only

Convert one city's local time into one or more other cities. The result includes a https://timeofmeeting.com link for a 60-minute meeting. Choose a different length with create_meeting_link.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Cities to convert into. An array, or one comma-separated string. City name or a city id from search_cities. Spelling and accents are flexible.
`from`	Yes	The city the clock time belongs to. City name or a city id from search_cities. Spelling and accents are flexible.
`time`	Yes	Local time in the from city, YYYY-MM-DD HH:MM or YYYY-MM-DDTHH:MM.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes
`utc`	Yes
`from`	Yes
`link`	Yes
`error`	No
`links`	Yes
`candidates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "candidates": {
+      "items": {
+        "properties": {
+          "country": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "region": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "type": "string"
+    },
+    "from": {
+      "properties": {
+        "country": {
+          "type": "string"
+        },
+        "kind": {
+          "type": "string"
+        },
+        "link": {
+          "type": "string"
+        },
+        "local": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "offset": {
+          "type": "string"
+        },
+        "region": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "weekend": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "zone": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "zone",
+        "local",
+        "offset",
+        "kind",
+        "link"
+      ],
+      "type": "object"
+    },
+    "link": {
+      "type": "string"
+    },
+    "links": {
+      "properties": {
+        "google": {
+          "type": "string"
+        },
+        "ics": {
+          "type": "string"
+        },
+        "meeting": {
+          "type": "string"
+        },
+        "planner": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "meeting",
+        "planner",
+        "ics",
+        "google"
+      ],
+      "type": "object"
+    },
+    "to": {
+      "items": {
+        "properties": {
+          "country": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "link": {
+            "type": "string"
+          },
+          "local": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "offset": {
+            "type": "string"
+          },
+          "region": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "weekend": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "zone": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "zone",
+          "local",
+          "offset",
+          "kind",
+          "link"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "utc": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "link",
+    "utc",
+    "from",
+    "to",
+    "links"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: the output always contains a timeofmeeting.com link scoped to a fixed 60-minute meeting, which an agent would not otherwise know.

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, zero padding. What the tool does comes first, the link caveat and its escape hatch follow immediately.

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?

An output schema exists so return values need no elaboration, and the description covers the surprising fixed-60-minute behavior plus the alternative for other lengths. It omits timezone/ambiguity handling, but the schema's strict time pattern and city parameters largely cover the call path.

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%, and the parameter docs already explain city names/ids, flexible accents, the array form, and the time format. The description adds nothing beyond 'one or more other cities', so the baseline 3 applies.

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?

States a specific verb and resource ('Convert one city's local time into one or more other cities'), and distinguishes itself from the sibling create_meeting_link by naming it directly. An agent can place this among current_time_in_cities and find_best_meeting_time without opening any schema.

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?

Gives an explicit routing rule: if you want a meeting length other than 60 minutes, use create_meeting_link. However it offers no guidance on when to prefer this over find_best_meeting_time or current_time_in_cities, which is left implicit.

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 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?