findtime.io MCP Server

Update my booking page

update_booking_page

DestructiveIdempotent

Updates the host's main meeting type lengths, weekly hours, page pause state, and agent booking setting. Hours are clock ranges in the host's zone; days left out keep their hours, and [] closes a day. Without confirm: true, the operation changes nothing and returns a read-back with status needs_confirmation. confirm: true executes the same operation after the person has confirmed that read-back. Every result has a status listed in the output schema. temporarily_unavailable indicates a temporary service failure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_booking_page"
  }
}

Input Schema

Name	Required	Description
`paused`	No	true stops new requests; false takes the page off pause.
`confirm`	No	true indicates the person confirmed the read-back returned by the same operation with confirmation omitted.
`durations`	No	Meeting lengths in minutes, like [30, 60].
`_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.
`weeklyHours`	No	Weekday to clock ranges, like {"monday": ["09:00-12:00", "13:00-17:00"], "friday": []}.
`agentBooking`	No	true lets guests' AI agents read times and send requests.
`defaultDuration`	No	The length the page offers first; one of durations.

Output Schema

Name	Required	Description	Default
`hint`	No
`page`	No
`error`	No
`reason`	No
`status`	Yes
`summary`	No
`readBack`	No
`freeMeetings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (which only declare destructive/idempotent/openWorld): it discloses the dry-run-first safety pattern, the needs_confirmation read-back, partial-update semantics for hours, and the meaning of the temporarily_unavailable status. For a destructive mutation this is exactly the behavioral context an agent needs before calling.

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?

Front-loaded with the action and affected fields, then the confirm protocol, then result statuses — logical ordering with little waste. The final line about statuses being in the output schema is slightly redundant given an output schema exists, but it usefully points the agent there.

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 a destructive, nested-object, 7-parameter mutation with an output schema, the description covers the confirmation workflow, partial-update behavior, and status semantics — everything an agent needs to invoke it safely. Return-value detail is correctly delegated to the output schema.

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 100%, so the schema already documents each field; the description nonetheless adds merge semantics for weeklyHours (omitted days retain hours, [] closes a day) that the schema only hints at via example. The remaining fields (paused, durations, agentBooking, defaultDuration) are covered by the schema alone, so this is above baseline but not exhaustive.

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 (updates) and resource (the host's booking page) and enumerates the exact facets touched: meeting lengths, weekly hours, pause state, and agent booking. This clearly separates it from the read-only sibling get_my_booking_page without the agent needing to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The confirm protocol is spelled out precisely: without confirm:true nothing changes and a read-back with status needs_confirmation is returned; confirm:true executes after the person confirms. Usage of the weeklyHours parameter is also disambiguated ('days left out keep their hours, and [] closes a day'). It stops short of naming sibling alternatives (e.g., get_my_booking_page for inspection), so not a 5.

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.