Time of Meeting

Find a fair meeting time

find_best_meeting_time

Read-only

Propose up to three fair meeting times while the slot is still being chosen. Ranking does not take a meeting length. Each slot has a score and the reasons. The result has one https://timeofmeeting.com link that opens the planner with those cities, and next_step, which says the user can choose a duration when creating the invitation. It does not include calendar files or a QR code. After a slot is chosen, call create_meeting_link.

Input Schema

TableJSON Schema

Name	Required	Description
`cities`	Yes	Two to eight cities. An array, or one comma-separated string. City name or a city id from search_cities. Spelling and accents are flexible.
`end_date`	No	Last day, YYYY-MM-DD. Defaults to six days after the start. At most 31 days.
`start_date`	No	First day, YYYY-MM-DD. Defaults to today (UTC).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`link`	Yes
`note`	Yes
`error`	No
`slots`	Yes
`cities`	Yes
`end_date`	Yes
`next_step`	Yes
`candidates`	No
`start_date`	Yes

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"
+    },
+    "cities": {
+      "items": {
+        "properties": {
+          "country": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "link": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "native": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "query": {
+            "type": "string"
+          },
+          "region": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "zone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "link"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "end_date": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "link": {
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "slots": {
+      "items": {
+        "properties": {
+          "cities": {
+            "items": {
+              "properties": {
+                "country": {
+                  "type": "string"
+                },
+                "dst": {
+                  "type": [
+                    "object",
+                    "null"
+                  ]
+                },
+                "kind": {
+                  "type": "string"
+                },
+                "local_end": {
+                  "type": "string"
+                },
+                "local_start": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "offset": {
+                  "type": "string"
+                },
+                "weekend": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "zone": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "name",
+                "zone",
+                "local_start",
+                "local_end",
+                "offset",
+                "kind"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "end": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "reasons": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "score": {
+            "type": "number"
+          },
+          "shifted": {
+            "type": "boolean"
+          },
+          "start": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "score",
+          "label",
+          "shifted",
+          "start",
+          "end",
+          "reasons",
+          "cities"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "start_date": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "link",
+    "start_date",
+    "end_date",
+    "cities",
+    "slots",
+    "next_step",
+    "note"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this a safe, read-only, closed-world operation, so the bar is lower. The description still adds genuine behavioral traits beyond them: ranking ignores meeting length, each slot carries a score and reasons, the result contains a planner link plus a next_step field, and it explicitly excludes calendar files and QR codes. Some of the return-format detail overlaps the output schema, keeping it short of a 5.

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?

Purpose is front-loaded in the first sentence, and each subsequent sentence carries usable information. It is slightly scattered—the exclusion sentence ('does not include calendar files or a QR code') and the link description could be tightened—but nothing is wasted.

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?

With full schema coverage and an output schema present, the description need not re-explain return values, yet it still covers scope, ranking semantics, output highlights, and sibling routing. Complete for correct invocation, with minor redundancy against the output schema as the only blemish.

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 description adds no parameter-level detail (no mention of cities limits or date ranges). Per the rubric, full schema coverage yields a baseline of 3 regardless of description depth.

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 (propose) and resource (up to three fair meeting times) with a clear scope qualifier ('while the slot is still being chosen'). An agent can distinguish it from create_meeting_link, which is explicitly the post-selection step, without opening either schema.

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?

Gives both the when-to-use condition ('while the slot is still being chosen') and the explicit alternative with its trigger ('After a slot is chosen, call create_meeting_link'). The routing decision is fully determined by the description.

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?