Zovo Meeting Planner

Convert time between time zones

convert_time

Read-onlyIdempotent

Use this when the user wants to convert a time between time zones or cities (time zone converter, e.g. 'convert 3pm PST to IST', 'time zone converter New York to London', 'what time is 9am EST in Warsaw on Nov 3'). Takes a date, a time, a source place (city, IANA zone, US state, country, UTC offset, or abbreviation) and up to 20 target places; returns the same instant in each place with UTC offset, abbreviation, +1/-1 day shift, the hour difference, and a note when a daylight saving change happens within 7 days. Explains times that are skipped or repeated by DST changes. Does not plan meetings (find_meeting_time covers that), look up flight times, or convert units.

Input Schema

Name	Required	Description
`to`	Yes	Target places in the same formats, e.g. ["London", "Asia/Kolkata", "Sydney"].
`date`	No	Local date at the source place as YYYY-MM-DD, e.g. 2026-11-03. Defaults to today at the source. Always pass it when the user names a day, because DST depends on the date.
`from`	Yes	Source place: a city ("New York", "Portland, Oregon"), an IANA zone ("Europe/Warsaw"), a US state, a country, a UTC offset ("UTC+5:30"), or an abbreviation ("PST", "CET", "IST"). Abbreviations mean the region's local clock on that date; ambiguous ones (IST, CST, AST, BST) use the first meaning and say so.
`time`	No	Local time at the source place, 24-hour or 12-hour, e.g. "15:00", "3pm", "9:30 am". Omit (with date) to convert the current moment.

Output Schema

Name	Required	Description	Default
`kind`	Yes
`notes`	Yes
`status`	Yes
`primary`	Yes
`alternate`	Yes
`status_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description still adds substantial context: it discloses the return contents (UTC offset, abbreviation, +/-1 day shift, hour difference, 7-day DST warning) and states it explains skipped or repeated local times caused by DST. That is real behavioral detail beyond the structured fields.

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?

One dense but well-ordered paragraph: trigger first, then inputs/return shape mid-way, then exclusions last. Every sentence carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter conversion tool with annotations and an output schema, the description covers trigger, input formats, output shape, DST edge cases, and out-of-scope uses. Nothing an agent needs in order to call it correctly 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 100%, so baseline is 3. The description nonetheless reinforces accepted source formats (city, IANA zone, US state, country, UTC offset, abbreviation), the max 20 targets, and the ambiguity handling for IST/CST/AST/BST, adding usable phrasing that eases correct invocation.

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 (convert) and resource (time between time zones/cities), and gives concrete example phrasings such as 'convert 3pm PST to IST'. It also names the sibling it is not (find_meeting_time), so an agent can distinguish them 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?

Opens with an explicit 'use this when' trigger, then lists explicit exclusions: does not plan meetings (routing to find_meeting_time), does not look up flight times, does not convert units. When-to-use and when-not-to-use are both covered with the alternative named.

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

All Zovo Meeting Planner 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?