Skip to main content
Glama
World Time MCP Server

World Time MCP Server

compare_times

Read-only

Retrieve the current local time in multiple cities at once to compare time zones and coordinate across locations.

Instructions

Get the current local time in several cities at once.

Args: cities: City names or IANA zones, e.g. ["Colombo", "London", "New York"].

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": "compare_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the batch behavior but says nothing about what happens with an unrecognized city name, duplicates, or limits on the number of cities.

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?

One-sentence purpose followed by a short Args block is front-loaded and free of filler. Slightly longer than strictly necessary but every line is useful.

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 not be explained, and the tool is simple with one parameter. The description covers purpose, input format, and an example; only edge-case behavior is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter, so the description carries the burden: it specifies acceptable values as city names OR IANA zones and gives a concrete example array. That is meaningful added meaning beyond the bare string array schema, though no fallback/error semantics are given.

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?

States a specific verb+resource (get the current local time) and the key scope distinction ('in several cities at once'), which separates it from a single-city get_time sibling. Sibling alternatives are not named explicitly, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by 'several cities at once' – an agent can infer this is the batch variant, but there is no explicit when-to-use/when-not guidance or reference to convert_time/get_time.

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

Deploy Server

Other Tools