findtime.io MCP Server

Get my booking page

get_my_booking_page

Read-onlyIdempotent

Returns the host's own findtime.io booking page. Link, meeting lengths, weekly hours in their zone, paused or private, passcode on or off, the agent booking switch, free meetings used and left, and active personal invite links. 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": "get_my_booking_page"
  }
}

Input Schema

Name	Required	Description	Default
`_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
`link`	No
`page`	No
`error`	No
`reason`	No
`status`	Yes
`summary`	No
`inviteLinks`	No
`freeMeetings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by listing the returned booking-page state fields and explaining that every result carries an output-schema status, with temporarily_unavailable meaning a temporary service failure.

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?

The description is front-loaded with the core purpose and then enumerates relevant return fields with minimal filler. The field list makes it slightly long, but each item is substantive.

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?

Given a simple one-parameter read-only tool, rich annotations, and an output schema, the description is largely complete: it names the resource, summarizes returned fields, and explains status behavior. The main missing element is explicit sibling routing, which is addressed under usage guidelines rather than completeness.

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?

The sole optional _endUserId parameter has 100% schema description coverage, so the schema already fully documents it. The description adds no parameter semantics beyond the schema, which matches the baseline 3 for high-coverage schemas.

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 states a specific verb and resource: it returns the host's own findtime.io booking page. The enumerated fields make the scope concrete, though it does not explicitly distinguish this from the related get_host_booking_profile sibling.

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 implied by the name and by 'host's own booking page,' but there is no explicit when-to-use guidance or comparison with alternatives such as get_host_booking_profile or update_booking_page. An agent can infer the use case, but the description does not route it among siblings.

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.