@findtime/mcp-server

get_overlap_hours

Read-onlyIdempotent

Calculate shared business-hours overlap across multiple locations, optionally for a specific date, so you can find mutually available meeting times.

Instructions

Return shared business-hours overlap across multiple locations using the production overlap endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Route vague or mixed-intent raw prompts to answer_time_question.

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": {
      "locations": "<locations>"
    },
    "name": "get_overlap_hours"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional date used to compute overlap. Prefer ISO YYYY-MM-DD, but simple human values such as "Thursday", "tomorrow", or "next Friday" are accepted.
`locations`	Yes
`_endUserId`	No	Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID.
`countryCodes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.28.1Nov 2, 2026

changedInput schema / properties / date / description

Previous value: -"Optional ISO date used to compute overlap."New value: +"Optional date used to compute overlap. Prefer ISO YYYY-MM-DD, but simple human values such as \"Thursday\", \"tomorrow\", or \"next Friday\" are accepted."

First observedv3.27.0Aug 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds a non-obvious runtime behavior: human-readable dates resolve relative to the first location's timezone. It does not describe the response shape or rate limits, keeping it from a 5.

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?

Four short sentences, front-loaded with purpose and usage guidance. There is slight redundancy with the schema on accepted date values, and the 'production overlap endpoint' phrase is not especially informative, but overall it is efficient.

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 four-parameter, read-only overlap tool with no output schema, the description supplies enough to select and invoke it correctly: purpose, required structured locations, optional date, and sibling routing. Return-value structure and countryCodes semantics are left to the schema or API.

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 50% and the schema already documents the accepted date and locations formats, including array joining. The description adds timezone resolution for date but does not explain countryCodes alignment or _endUserId, though _endUserId is host-populated.

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 and resource: 'Return shared business-hours overlap across multiple locations.' It also explicitly distinguishes itself from answer_time_question for vague or mixed-intent prompts, so an agent can separate it from siblings.

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 an explicit use condition ('structured locations and, optionally, a date') and an explicit alternative for vague raw prompts ('answer_time_question'). This covers both when to use this tool and when to route elsewhere.

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

Deploy Server