findtime.io MCP Server

Check a proposed meeting time

check_proposed_time

Read-onlyIdempotent

Evaluates a proposed meeting instant for each city. start accepts an ISO instant or a floating local time with home set to an IANA timezone. The result includes the UTC instant, local times, verdicts, formatted shareText, and up to three alternative aiSlots. A context field describes any skipped or repeated local time caused by daylight saving changes.

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": {
      "start": "<start>"
    },
    "name": "check_proposed_time"
  }
}

Input Schema

Name	Required	Description
`date`	No	YYYY-MM-DD when start is only a clock time.
`home`	No	IANA timezone for a floating start, such as America/Los_Angeles.
`start`	Yes	ISO instant with a UTC offset, or a floating local time such as 2026-09-29T09:00 or 9:00am.
`teamId`	No	Exact homepage Saved group name. A signed-in hosted agent loads that group when locations are omitted. Marketing and marketing are two groups. Without an account, returns teams_not_persisted.
`workEnd`	No	Last in-hours local hour, inclusive. Default 18.
`locations`	No
`workStart`	No	First in-hours local hour. Default 9.
`_endUserId`	No	Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Accepts a non-PII hash or token, excluding raw email addresses, names, or platform user IDs.
`countryCodes`	No
`durationMinutes`	No	Optional. Only 30, 45, or 60 are written onto the planner link.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful behavior beyond that: it enumerates the response shape (UTC instant, local times, verdicts, shareText, up to three aiSlots) and calls out the DST 'context' field for skipped/repeated local times — genuinely informative for interpreting results.

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?

Three sentences, front-loaded with the action, then input semantics, then return shape — no filler. Slightly dense but every clause carries information an agent would otherwise have to discover.

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?

With no output schema, the description compensates by summarizing the return payload, and with 10 params it covers the tricky ones (start/home interplay, DST context). What it omits is the routing information — when this beats find_meeting_time — which is the main remaining gap for a 33-sibling toolset.

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 already 80%, so the baseline is 3, but the description adds a cross-parameter relationship the schema does not state: a floating start must be paired with home as an IANA timezone. That is real semantic value beyond the per-field text.

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 opens with a specific verb and resource: 'Evaluates a proposed meeting instant for each city.' That is clearly distinct from an optimal-slot finder, but it never names the appropriate sibling (find_meeting_time, find_host_slots, answer_time_question) so the agent must infer the boundary from the name alone.

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 by the word 'proposed' — the agent can guess this is the verify-this-slot tool rather than the discover-a-slot tool. There is no explicit when-to-use statement, no exclusion of find_meeting_time or answer_time_question, and no note on prerequisites such as needing locations or a teamId.

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

All findtime.io MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.