Skip to main content
Glama

Time of Meeting

Current time in cities

current_time_in_cities
Read-onlyIdempotent

World clock: show the current local time, IANA time zone, UTC offset, work-hour band, and public holiday, if that date is one, for each city. Use when the user asks what time it is now in one or more cities. The result includes a https://timeofmeeting.com link that opens the planner for the first city. weeks is the ISO week and the US week of the UTC date.

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": {
      "cities": "<cities>"
    },
    "name": "current_time_in_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesYesOne to eight cities. An array, or one comma-separated string. 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.

Output Schema

NameRequiredDescriptionDefault
utcYes
linkYes
errorNo
weeksYesISO 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).
citiesYes
candidatesNo
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 / cities / description
      Previous value: -"One to eight cities. An array, or one comma-separated string. 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: +"One to eight cities. An array, or one comma-separated string. 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. Changed2 schema fields changed
    • addedOutput schema / 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 / required
      Previous value: -[
      -  "link",
      -  "utc",
      -  "cities"
      -]New value: +[
      +  "link",
      +  "utc",
      +  "weeks",
      +  "cities"
      +]
  3. Changed4 schema fields changed
    • changedInput schema / properties / cities / description
      Previous value: -"One to eight cities. An array, or one comma-separated string. City name or a city id from search_cities. Spelling and accents are flexible."New value: +"One to eight cities. An array, or one comma-separated string. 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"
      +}
    • addedOutput schema / properties / cities / items / properties / holiday
      Added value: +{
      +  "properties": {
      +    "date": {
      +      "type": "string"
      +    },
      +    "label": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "name_en": {
      +      "type": "string"
      +    },
      +    "regional": {
      +      "type": "boolean"
      +    },
      +    "regions": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "name",
      +    "name_en",
      +    "regional",
      +    "regions",
      +    "label",
      +    "source"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / cities / items / required
      Previous value: -[
      -  "name",
      -  "zone",
      -  "local",
      -  "offset",
      -  "kind",
      -  "link"
      -]New value: +[
      +  "name",
      +  "zone",
      +  "local",
      +  "offset",
      +  "kind",
      +  "holiday",
      +  "link"
      +]
  4. Changed1 schema field changed
    • 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"
      +          },
      +          "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"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "link": {
      +      "type": "string"
      +    },
      +    "utc": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "link",
      +    "utc",
      +    "cities"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds a genuinely useful behavioral note—that a timeofmeeting.com planner link is returned for the first city—but the remaining sentences describe return fields, which the output schema already carries.

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?

The purpose and usage trigger are front-loaded in the first two sentences with no filler. The trailing sentence about 'weeks is the ISO week and the US week of the UTC date' is output-field detail that belongs with the output schema and reads slightly out of place here.

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 a full output schema, complete annotations, and one well-documented parameter, the description supplies the purpose, trigger, and the notable planner-link side effect, which is enough to call the tool correctly. The only ambiguity-resolution path (fall back to search_cities for an unknown city) is left implicit.

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% and the singular 'cities' parameter is documented richly in-schema (1–8 items, comma-separated string accepted, fuzzy spelling/accents, alternatives returned on name collisions). The description adds no parameter meaning beyond that, so the baseline of 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?

The description opens with a concrete verb-plus-resource statement ('show the current local time, IANA time zone, UTC offset, work-hour band, and public holiday') and scopes it per city. It is clearly separable from siblings like convert_time, dst_check, or get_holidays because it returns a composite snapshot for named cities rather than converting or checking a single concern.

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 states the trigger condition explicitly: 'Use when the user asks what time it is now in one or more cities.' That is strong when-to-use guidance. It does not name alternatives (e.g., use convert_time for an arbitrary target moment, or search_cities to resolve ambiguous names), so no when-not guidance exists.

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