findtime.io MCP Server

List my incoming booking requests

list_booking_requests

Read-onlyIdempotent

Lists the host's booking requests with guest name and email, explicit times in the host's zone, an agent-origin tag, status, lifecycleVersion, and permitted actions. olderRequests contains the count and inbox link for older requests available only on the website. Every result has a status listed in the output schema. temporarily_unavailable indicates a temporary service failure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_booking_requests"
  }
}

Input Schema

Name	Required	Description
`to`	No	ISO date in the host's zone: requests starting on or before it.
`from`	No	ISO date in the host's zone: requests starting on or after it.
`status`	No	pending, confirmed, declined, cancelled_by_guest, cancelled_by_host, a comma list, or all (default).
`_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.

Output Schema

Name	Required	Description	Default
`hint`	No
`error`	No
`reason`	No
`status`	Yes
`summary`	No
`requests`	No
`olderRequests`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world. The description adds real behavior: host-zone time normalization, agent-origin tagging, permitted actions per row, and a temporarily_unavailable flag for service failure — context not in the annotations.

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 purpose then packs only return-relevant facts into a few tight sentences with no filler. Every clause (olderRequests, status, temporarily_unavailable) earns its place.

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?

With an output schema present and full annotation coverage, the description need only flag non-obvious behavior, which it does (timezone, olderRequests website-only, transient failure). Complete enough for an agent to call correctly.

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 to/from/status/_endUserId are fully documented in the schema and baseline is 3. The description adds no filtering or parameter meaning beyond what the schema provides.

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?

Specific verb+resource ("Lists the host's booking requests") plus a clear inventory of what's returned. It never distinguishes itself from the near-identical sibling list_my_booking_requests, though the added return-content and olderRequests/website details give it a distinct feel.

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 the listing behavior rather than stated: no when-to-use/when-not guidance and no routing to alternatives like list_my_booking_requests. It does usefully note that older requests are available only on the website and that temporarily_unavailable means a transient failure, which are partial usage hints.

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.