Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_geo_global_scheduling_composite

Find meeting slots that fall inside working hours for every participant timezone, skipping weekends and public holidays, with per-participant local times.

Instructions

[Global Locale] Find meeting slots that fall inside working hours for every participant timezone, skipping weekends and public holidays, with per-participant local times Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://geo.caelaralabs.com.

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": {
      "timezones": "<timezones>"
    },
    "name": "caelara_geo_global_scheduling_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOrganizer-local date YYYY-MM-DD (default today)
work_endNoWorking day end HH:MM (default 17:00)
countriesNoComma list of ISO alpha-2 codes aligned with timezones, used to skip public holidays
timezonesYesComma list of IANA timezones; the first is the organizer whose local day anchors the search
work_startNoWorking day start HH:MM (default 09:00)
duration_minutesNoMeeting length in minutes (default 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that weekends and public holidays are excluded, that results carry per-participant local times, latency figures, and that an external host is called — but it says nothing about side effects, auth requirements, rate limits, or the exact shape of the returned slots.

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 core capability is front-loaded in a single dense sentence, followed by benchmark provenance and endpoint. Both trailing items are compact and mildly useful, though the benchmark timestamp is closer to marketing metadata than invocation guidance.

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

Completeness3/5

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

For a six-parameter composite with no annotations and no output schema, the description should clarify what the caller receives (a ranked list of slots? per-participant blocks?) and how errors such as unknown IANA zones surface. 'Per-participant local times' hints at the payload but does not fully cover return semantics.

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%, so the schema already documents every parameter including defaults and the organizer-anchoring rule for the first timezone. The description only reinforces the holiday-skipping role of the countries list and the per-timezone working-hours filter, adding little beyond the structured fields.

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 and resource ('Find meeting slots') plus concrete scope conditions (working hours per timezone, weekends and holidays skipped, per-participant local times). An agent can distinguish this from a plain timezone converter or business-hours calculator, though it never names those siblings explicitly.

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?

The scheduling framing implies when to reach for it, but there is no explicit when-to-use/when-not guidance and no mention of the sibling tools (e.g. caelara_geo_business_hours_calc, caelara_geo_timezone_converter) that cover adjacent single-purpose cases.

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