findtime.io MCP Server

Get a host's booking profile

get_host_booking_profile

Read-onlyIdempotent

Reads a findtime.io host's booking profile for a guest, including name, time zone, meeting lengths, meeting types, minimum notice, and passcode requirement. handle accepts the exact host handle or booking-page link; first names alone are not searchable. The host sets the meeting location on approval and approves or declines every request. Every result has a status. ok contains the answer. needs_clarification contains a question and candidate retry arguments. no_match reasons include host_not_found, host_busy_in_window with nearest alternatives, outside_booking_window, duration_not_offered, and host_not_taking_requests. temporarily_unavailable indicates a temporary service failure.

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": {
      "handle": "<handle>"
    },
    "name": "get_host_booking_profile"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	The host's findtime.io handle, or their findtime.io/b/<handle> link.
`_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.

Output Schema

Name	Required	Description	Default
`hint`	No
`host`	No
`error`	No
`reason`	No
`status`	Yes
`summary`	No
`approval`	No
`location`	No
`durations`	No
`meetingTypes`	No
`takingRequests`	No
`defaultDuration`	No
`passcodeRequired`	No
`bookingWindowDays`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations that already mark this as read-only, idempotent, and non-destructive, the description discloses the host approval workflow, that every result has a status, and that no_match reasons include specific cases like host_not_found or duration_not_offered. It also explains temporarily_unavailable, adding meaningful operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and profile contents, then follows with input constraints and result-status behavior. Every sentence adds information an agent needs to call or interpret the tool correctly.

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?

With annotations covering safety and idempotency and an output schema present, the description is complete enough for invocation. It also explains the status envelope and no_match reasons, which are important for interpreting results.

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 both parameters. The description adds useful semantics for handle by clarifying accepted formats and that first names are not searchable, though it does not discuss the optional _endUserId parameter.

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?

The description uses a specific verb and resource: it reads a findtime.io host's booking profile for a guest and enumerates the profile fields included. This clearly distinguishes it from sibling tools such as find_host_slots or get_booking_status.

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?

It gives clear input usage constraints, including that handle accepts an exact host handle or booking-page link and that first names alone are not searchable. It does not explicitly name alternatives or when-not-to-use cases, so it stops short of 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.