findtime.io MCP Server

Decline a booking request

decline_booking_request

DestructiveIdempotent

Declines a host booking request. The guest sees it as declined. 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": "decline_booking_request"
  }
}

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.3/5.0

Behavior5/5

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

Annotations only declare destructive/idempotent hints; the description adds the crucial two-phase dry-run semantics ('without confirm: true, the operation changes nothing'), the guest-facing consequence, and the meaning of the needs_confirmation and temporarily_unavailable statuses — behavior an agent could not infer from structured fields alone.

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?

Five short, front-loaded sentences; the confirm/read-back protocol precedes the status caveats, and no sentence is filler.

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 an output schema present the return values need no explanation, and annotations cover mutation safety. The description supplies exactly the missing layer — dry-run flow, user-visible effect, and status semantics — leaving nothing an agent needs before calling.

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 confirm, reason, lifecycleVersion and _endUserId are already documented. The description's explanation of confirm largely restates the schema's own wording, so it adds little beyond the baseline.

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 ('Declines a host booking request') and clarifies the guest-visible effect. It does not, however, distinguish itself from siblings such as cancel_booking or cancel_booking_as_host, which an agent could plausibly confuse with declining a request.

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 guidance: call without confirm to get a read-back, then call again with confirm: true once the person has confirmed. It does not explain when declining is the right action versus cancelling or rescheduling, but the invocation protocol is unambiguous.

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.