findtime.io MCP Server

Reschedule my booking request

reschedule_booking

Destructive

Moves a pending request to another available option for the same host. Withdraws the old request and sends a new one. Approved meetings cannot be moved through this tool and return no_match with reason confirmed_needs_host. 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>",
      "optionId": "<optionId>"
    },
    "name": "reschedule_booking"
  }
}

Input Schema

Name	Required	Description
`invite`	No	The invite value, if the request came from a personal link.
`confirm`	No	true indicates the person confirmed the read-back returned by the same operation with confirmation omitted.
`optionId`	Yes	The new time, identified by an optionId from a recent availability response for the same host.
`passcode`	No	The page passcode, if the page has one.
`guestZone`	No	The guest's IANA time zone.
`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
`options`	No
`request`	No
`summary`	No
`readBack`	No
`guestHistoryToken`	No
`replacedRequestId`	No
`guestTrackingToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- changedOutput schema / properties / guestHistoryToken / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing what is destroyed (the old request is withdrawn and replaced), the confirmation gate that makes a no-confirm call a no-op, and the failure semantics (no_match / confirmed_needs_host, temporarily_unavailable). It does not mention permission or auth requirements for acting on another person's request, so it stops short of the top score despite the destructiveHint already flagging risk.

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?

Front-loads the core action, then the exclusion, then the confirmation protocol, then the status vocabulary — each sentence carries a distinct operational fact with no filler. Dense but well ordered for an agent reading top-down.

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?

For a destructive, open-world mutation with a confirmation handshake, the description covers the action, the exclusion case, the no-op case, and the error vocabulary. Return values are backed by an output schema, so nothing an agent needs in order to invoke this correctly is missing.

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 100%, so all nine parameters are already documented in structured form, and the description largely restates the confirm protocol that the schema also explains. It does add the constraint that optionId must come from a recent availability response for the same host, but that is also in the schema description, so it earns the baseline rather than more.

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?

States a specific verb and resource ('Moves a pending request to another available option for the same host') and immediately clarifies the underlying mechanics ('Withdraws the old request and sends a new one'). An agent can distinguish this from cancel_booking or request_booking without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly scopes out a whole class of usage: 'Approved meetings cannot be moved through this tool and return no_match with reason confirmed_needs_host.' It also prescribes the exact two-call protocol (call without confirm, show read-back, then call with confirm: true), which is when-to-use guidance of the highest order.

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.