findtime.io MCP Server

Cancel my booking

cancel_booking

DestructiveIdempotent

Cancels the guest's request or approved meeting. findtime.io emails the host, and an approved meeting's calendar event is removed. 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": {
      "requestId": "<requestId>"
    },
    "name": "cancel_booking"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional reason for the host.
`confirm`	No	true indicates the person confirmed the read-back returned by the same operation with confirmation omitted.
`requestId`	Yes	requestId from an earlier answer.
`_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.
`guestHistoryToken`	No	guestHistoryToken returned with the request; grants access to this guest's requests to that host.
`guestTrackingToken`	No	guestTrackingToken returned when this request was created.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses that the host is emailed, that an approved meeting's calendar event is removed, and that missing confirmation produces a no-op read-back with needs_confirmation. It also explains the temporary_unavailable status, giving rich behavioral context for a destructive operation.

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 immediately explains the confirmation workflow. Every sentence contributes relevant behavioral detail without redundancy.

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?

The tool is destructive with an output schema, and the description covers the confirmation safety flow, side effects, and status references. An agent has enough information to invoke it correctly without needing return-value details.

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 description coverage is 100%, so the schema already documents requestId, confirm, reason, and the token fields. The description reinforces the confirm semantics but does not add substantial parameter guidance beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb, resource, and scope: it cancels a guest's request or approved meeting. The word 'guest' implicitly distinguishes this from the sibling cancel_booking_as_host, and it names the concrete side effects (host email, calendar removal).

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 clearly explains the two-step confirmation workflow: without confirm:true nothing changes and a read-back is returned; with confirm:true the operation executes. It does not explicitly mention when to choose a sibling like cancel_booking_as_host, but the guest-specific scope gives strong implied guidance.

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.