OperatorNest tools

Meeting time zones

meeting_time_zones

Read-onlyIdempotent

Find shared 30-minute meeting slots inside 09:00–17:00 for 2–8 participants. Use to compare workday overlap; use recurring_schedule for repeating task calendars or cron_next_runs for scheduler previews. Returns all candidates, overlap count and up to three best slots ranked nearest to each person’s 13:00, with UTC starts and local labels. The date belongs to the first participant’s zone; daylight saving uses runtime IANA data. No calendar availability or holiday lookup, invitations or calendar writes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Meeting date in the first person’s local time zone, from 2000-01-01 to 2100-12-31.
`people`	Yes	Participants in display order. The first person determines the local date; all must fit a full half-hour inside 09:00–17:00.

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	Yes	All candidate half-hour starts on the first participant’s local date, in chronological order.
`tool`	Yes	Calculator identifier for this result.
`input`	Yes	Normalized inputs used for this calculation.
`units`	Yes	Units for the numeric and time fields in this result.
`method`	Yes	Calculation or ranking method applied to the inputs.
`bestSlots`	Yes	Up to three shared slots ranked by score, then earliest UTC start; [] means no overlap.
`provenance`	Yes	Dated data sources or runtime time-zone information used for this result.
`assumptions`	Yes	Limits and assumptions to retain when presenting the result.
`overlapCount`	Yes	Number of candidate slots inside every participant’s workday.

Schema Changelog

Changes observed during successful MCP inspections.

Changed38 schema fields changedOct 3, 2026

changedInput schema / properties / date / description

Previous value: -"Real date from 2000-01-01 to 2100-12-31."New value: +"Meeting date in the first person’s local time zone, from 2000-01-01 to 2100-12-31."

addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-10-05"
+]
```
addedInput schema / properties / date / maxLength
```
Added value: +10
```
addedInput schema / properties / date / minLength
```
Added value: +10
```

addedInput schema / properties / people / description

Added value: +"Participants in display order. The first person determines the local date; all must fit a full half-hour inside 09:00–17:00."

addedInput schema / properties / people / items / properties / name / description
```
Added value: +"Participant label used in the returned local-time display."
```
addedInput schema / properties / people / items / properties / name / examples
```
Added value: +[
+  "Sam"
+]
```

changedInput schema / properties / people / items / properties / zone / description

Previous value: -"An IANA time zone supported by Intl.DateTimeFormat, such as America/New_York."New value: +"IANA time zone supported by Intl.DateTimeFormat."

addedInput schema / properties / people / items / properties / zone / examples
```
Added value: +[
+  "America/New_York",
+  "Asia/Kolkata"
+]
```

addedOutput schema / description

Added value: +"Meeting candidates and ranked shared slots with normalized participants, local labels and DST assumptions."

addedOutput schema / properties / assumptions / description

Added value: +"Limits and assumptions to retain when presenting the result."

addedOutput schema / properties / bestSlots / description

Added value: +"Up to three shared slots ranked by score, then earliest UTC start; [] means no overlap."

addedOutput schema / properties / bestSlots / items / properties / inside / description

Added value: +"Whether each participant’s full half-hour fits their 09:00–17:00 workday, in input order."

addedOutput schema / properties / bestSlots / items / properties / labels / description
```
Added value: +"Local start labels for participants in input order."
```

addedOutput schema / properties / bestSlots / items / properties / score / description

Added value: +"Sum of absolute hours from 13:00 at each participant’s slot midpoint; lower ranks first."

addedOutput schema / properties / bestSlots / items / properties / startUtc / description
```
Added value: +"Start instant in ISO 8601 UTC."
```

addedOutput schema / properties / input / description

Added value: +"Normalized inputs used for this calculation."

changedOutput schema / properties / input / properties / date / description

Previous value: -"Real date from 2000-01-01 to 2100-12-31."New value: +"Meeting date in the first person’s local time zone, from 2000-01-01 to 2100-12-31."

addedOutput schema / properties / input / properties / date / examples
```
Added value: +[
+  "2026-10-05"
+]
```
addedOutput schema / properties / input / properties / date / maxLength
```
Added value: +10
```
addedOutput schema / properties / input / properties / date / minLength
```
Added value: +10
```

addedOutput schema / properties / input / properties / people / description

Added value: +"Participants in display order. The first person determines the local date; all must fit a full half-hour inside 09:00–17:00."

addedOutput schema / properties / input / properties / people / items / properties / name / description
```
Added value: +"Participant label used in the returned local-time display."
```
addedOutput schema / properties / input / properties / people / items / properties / name / examples
```
Added value: +[
+  "Sam"
+]
```

changedOutput schema / properties / input / properties / people / items / properties / zone / description

Previous value: -"An IANA time zone supported by Intl.DateTimeFormat, such as America/New_York."New value: +"IANA time zone supported by Intl.DateTimeFormat."

addedOutput schema / properties / input / properties / people / items / properties / zone / examples
```
Added value: +[
+  "America/New_York",
+  "Asia/Kolkata"
+]
```

addedOutput schema / properties / method / description

Added value: +"Calculation or ranking method applied to the inputs."

addedOutput schema / properties / overlapCount / description

Added value: +"Number of candidate slots inside every participant’s workday."

addedOutput schema / properties / provenance / additionalProperties / description
```
Added value: +"Unit or source detail for the named field."
```

addedOutput schema / properties / provenance / description

Added value: +"Dated data sources or runtime time-zone information used for this result."

addedOutput schema / properties / rows / description

Added value: +"All candidate half-hour starts on the first participant’s local date, in chronological order."

addedOutput schema / properties / rows / items / properties / inside / description

Added value: +"Whether each participant’s full half-hour fits their 09:00–17:00 workday, in input order."

addedOutput schema / properties / rows / items / properties / labels / description
```
Added value: +"Local start labels for participants in input order."
```

addedOutput schema / properties / rows / items / properties / score / description

Added value: +"Sum of absolute hours from 13:00 at each participant’s slot midpoint; lower ranks first."

addedOutput schema / properties / rows / items / properties / startUtc / description
```
Added value: +"Start instant in ISO 8601 UTC."
```

addedOutput schema / properties / tool / description

Added value: +"Calculator identifier for this result."

addedOutput schema / properties / units / additionalProperties / description
```
Added value: +"Unit or source detail for the named field."
```

addedOutput schema / properties / units / description

Added value: +"Units for the numeric and time fields in this result."

First observedOct 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: DST resolved via runtime IANA data, the date belonging to the first participant's zone, and the ranking heuristic (nearest each person's 13:00). Slightly short of 5 only because pagination/limits on candidate count aren't addressed.

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?

Front-loaded with the core purpose, then alternatives, then return shape and edge cases. Four tight sentences, each carrying distinct information with no redundancy or 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?

An output schema exists so return values needn't be re-explained, and annotations cover safety. The description still fills the remaining gaps an agent needs – DST handling, date-zone anchoring, ranking rule, and explicit out-of-scope operations – making it complete for a two-parameter read tool.

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 the baseline is 3 and the schema carries the syntax. The description nonetheless reinforces semantics that matter for interpretation – that the date is anchored to the first participant's zone and that participants are ordered with the first determining the local date – which clarifies intent beyond raw field definitions.

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 (Find) and resource (shared 30-minute meeting slots) with concrete scope: 09:00–17:00 window and 2–8 participants. It explicitly names sibling tools (recurring_schedule, cron_next_runs) so the agent can distinguish it 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 Guidelines5/5

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

Gives positive guidance ("Use to compare workday overlap") and routes to alternatives by condition (recurring_schedule for repeating task calendars, cron_next_runs for scheduler previews). It also states what it is not for: calendar availability, holiday lookup, invitations, or calendar writes.

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

All OperatorNest tools tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.