findtime.io MCP Server

Create a personal invite link

create_invite_link

Creates a personal booking link for one guest, with their name and email locked on it. findtime.io returns the link without sending it to the guest. 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

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": {
      "guestName": "<guestName>",
      "guestEmail": "<guestEmail>"
    },
    "name": "create_invite_link"
  }
}

Input Schema

Name	Required	Description
`note`	No	A note the guest sees on the link.
`confirm`	No	true indicates the person confirmed the read-back returned by the same operation with confirmation omitted.
`subject`	No
`guestName`	Yes
`_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.
`guestEmail`	Yes
`expiresInDays`	No	Optional: the link stops working after this many days.
`durationMinutes`	No	One of the page's meeting lengths.

Output Schema

Name	Required	Description	Default
`url`	No
`hint`	No
`error`	No
`reason`	No
`status`	Yes
`summary`	No
`readBack`	No
`inviteLink`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that no email is sent to the guest, that omitting confirm is a true no-op, that confirm re-executes the same operation, and what temporarily_unavailable means. These are exactly the mutation-safety and side-effect facts an agent needs and that readOnlyHint=false/destructiveHint=false/idempotentHint=false cannot convey.

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 purpose, then the confirmation protocol, then status handling — a logical order with no wasted preamble. There is mild redundancy between the confirm sentences and the confirm parameter's own schema description.

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 an 8-parameter, non-idempotent mutation tool with an output schema, the description covers the critical gating protocol and side effects. It omits access prerequisites, default expiry behavior, and what happens if a link already exists for the same guest, which keeps it short of complete.

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 coverage is 63%, so the baseline is 3. The description adds real meaning for guestName/guestEmail (locked onto the link) and describes the confirm two-step flow, but subject, note, expiresInDays and durationMinutes are left entirely to the schema.

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?

States a specific verb and resource ('Creates a personal booking link for one guest') plus a distinguishing constraint (name and email locked on the link). It does not name the obvious sibling revoke_invite_link or explain how it differs from request_booking, so it falls short of full sibling differentiation.

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?

Gives clear operational context: call without confirm to get a read-back (status needs_confirmation) and only then re-call with confirm: true. That is an explicit when-to-do-what rule. It stops short of steering between this tool and alternatives such as request_booking or generic link creation.

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.