Skip to main content
Glama

Caelara Labs Global Locale

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

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": "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 observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the core semantics: weekends and public holidays are skipped and results carry per-participant local times. It omits important behavior such as what happens when no slot satisfies the constraints, whether there is a result limit, and how many candidate slots are returned.

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?

A single dense sentence with the resource and the most important constraints front-loaded; nothing is padding. The trailing 'with per-participant local times' phrase is slightly tacked on but still earns its place by signaling output content.

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?

For a six-parameter composite with a fully documented schema, the description covers the essential contract: what the search respects and what the output contains. The gaps are the no-annotations safety profile (read-only? side effects?) and the result shape when no slot is found, which is a moderate but not disqualifying omission.

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 explains each of the six parameters, including defaults and the organizer-anchoring rule for the first timezone. The description adds only the high-level intent (holiday skipping via countries, per-participant local output) and no syntax or edge-case detail beyond the schema, so the baseline 3 applies.

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?

The description uses a specific verb ('Find') with a concrete resource ('meeting slots') and layers on the defining constraints: working hours across every participant timezone, weekend and public-holiday exclusion, and per-participant local times. That is enough to distinguish it from simpler siblings like timezone_converter or public_holiday_lookup, though it never names a sibling it is the alternative to.

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: the scope statement (multi-timezone scheduling with working-hour and holiday constraints) tells an agent the situation it fits, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this is the composite path versus calling the atomic timezone/holiday tools separately.

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