Date Math

Find free meeting slots

find_free_slots

Read-onlyIdempotent

Find meeting times when everyone is free: intersects each participant's working hours (own time zone, workdays, country holidays) minus their busy blocks, then lists slots of the requested length. Up to 10 people, 14 days, optional buffer between meetings. Use for scheduling across calendars and time zones. First 25 calls per day are free, then $0.001 per call (x402).

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": {
      "participants": "<participants>",
      "duration_minutes": "<duration_minutes>"
    },
    "name": "find_free_slots"
  }
}

Input Schema

Name	Required	Description
`days`	No
`from`	No
`timezone`	No	Organizer's zone: defines the days searched and slot alignment (default: first participant's)
`work_end`	No	Default end of working hours, 17:00
`max_slots`	No
`not_before`	No	Earliest slot start: ISO 8601 with offset, or "now"
`work_start`	No	Default start of working hours, 09:00
`participants`	Yes
`step_minutes`	No	Slot start alignment
`buffer_minutes`	No	Free time kept around busy blocks
`duration_minutes`	Yes

Output Schema

Name	Required	Description	Default
`count`	Yes
`range`	Yes
`slots`	Yes
`timezone`	Yes
`free_windows`	Yes
`duration_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), yet the description still adds real behavioral facts: hard limits of 10 people and 14 days, optional buffer, and a cost/rate model (25 free calls/day, then $0.001 per call via x402). Billing and quota information is exactly the kind of context annotations cannot express.

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?

Purpose and algorithm are front-loaded in the first sentence, with constraints and pricing following. It is dense but each sentence carries information; the pricing clause is the only one that could be seen as tangential, though it is genuinely operationally relevant.

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 an 11-parameter computed-search tool with an output schema and annotations present, the description covers purpose, computation approach, scale limits, and cost. Nothing critical for correct invocation is missing, and return-value details are correctly left to the output schema.

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 coverage is 55%, so the schema already documents the most semantically loaded fields (timezone, busy blocks, workdays, holidays, buffer, step). The description reinforces the mental model of per-participant work hours minus busy blocks and restates the 10-person/14-day caps, but adds no format or precedence detail beyond structured fields, so the baseline 3 fits.

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 names a specific verb and resource ('Find meeting times') and goes further by stating the algorithm it applies: intersect working hours per participant's zone/workdays/holidays, subtract busy blocks, list slots of the requested length. It is clear which tool this is, but it never names the closest sibling (working_hours_overlap), so an agent must still infer the distinction.

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?

'Use for scheduling across calendars and time zones' gives a usage context but no exclusions or prerequisites, and there is a sibling (working_hours_overlap) that sounds functionally adjacent. The agent gets a rough sense of when to reach for this tool but no explicit when-not guidance.

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

All Date Math tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.