findtime.io MCP Server

Cancel a booking as host

cancel_booking_as_host

DestructiveIdempotent

Cancels a request or approved meeting as the host. The status changes first, then the Google 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>",
      "lifecycleVersion": "<lifecycleVersion>"
    },
    "name": "cancel_booking_as_host"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional reason for the guest.
`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.
`lifecycleVersion`	Yes	Request lifecycleVersion from the latest inbox response. A stale value returns conflict.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it explains the sequence of status change then Google Calendar event removal, the read-back behavior when confirm is omitted, the need for confirm: true, and the meaning of output statuses including temporary_unavailable. This is consistent with destructiveHint=true and idempotentHint=true.

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 action, then explains the confirmation flow and status handling in a compact sequence. Every sentence provides useful context for invoking or interpreting the operation.

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?

Given the destructive mutation, confirmation workflow, rich annotations, complete schema descriptions, and available output schema, the description covers what an agent needs to call the tool safely and interpret key results. No major contextual gap remains.

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 baseline is 3, but the description adds meaningful semantics for confirm by explaining the read-back/confirmation workflow and what happens when it is absent or true. It relies on the schema for requestId, lifecycleVersion, reason, and _endUserId.

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 ('Cancels a request or approved meeting') plus the actor role ('as the host'), which meaningfully scopes the operation. It does not explicitly distinguish this from nearby siblings such as cancel_booking or decline_booking_request, 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 Guidelines3/5

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

Usage is implied by 'as the host' and by the two-stage confirmation flow, but the description does not explicitly say when to choose this over cancel_booking or decline_booking_request. The confirm behavior is well explained, but alternative selection guidance is absent.

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.