findtime.io MCP Server

Check a booking request

get_booking_status

Read-onlyIdempotent

Checks one booking request with status waiting for the host, approved (with the meeting link or place once the host approves), declined or cancelled, with explicit times in the guest's and host's zones. 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>",
      "guestTrackingToken": "<guestTrackingToken>"
    },
    "name": "get_booking_status"
  }
}

Input Schema

Name	Required	Description
`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.
`guestTrackingToken`	Yes	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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond those annotations: the specific status set, that approved results include a meeting link or place, that times are shown in both guest and host zones, and that temporarily_unavailable indicates a temporary service failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the core operation. The status enumeration and timezone detail earn their place by clarifying output shape, though the sentence is slightly run-on.

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?

An output schema exists, so return values need not be fully described. The description still covers the status space and explicitly flags temporarily_unavailable, which is useful context for interpreting results. Nothing critical for correct invocation 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 description coverage is 100%, so the schema already documents requestId, guestTrackingToken, and _endUserId. The description adds no parameter-specific syntax or constraints beyond what the schema already 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?

States a specific verb and resource: 'Checks one booking request,' and enumerates the possible statuses including approved with meeting link/place. The 'one booking request' scope implicitly distinguishes it from sibling list tools like list_booking_requests, though it never names an alternative.

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 required parameters and by the phrase 'Checks one booking request,' but the description does not explicitly state when to use this versus list_booking_requests or list_my_booking_requests. No when-not guidance or named alternatives are provided.

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.