Yoya Booking

Confirm a reviewed meeting

book_meeting

Destructive

Creates a free booking or returns PAYMENT_REQUIRED with a secure payment URL for paid meetings. Paid meetings are not booked until payment succeeds; show the link and never claim confirmation before that. Only call after the guest explicitly approves preview_booking. Copy the preview's booking fields and confirmationToken unchanged. Reuse requestId and token on network retries; never claim notifications are delivered until syncStatus is ready.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`slug`	Yes
`email`	Yes
`slotId`	Yes
`purpose`	No
`timezone`	No
`confirmed`	Yes
`requestId`	No	Reuse the ID returned by preview_booking for retries.
`meetingType`	No
`fieldAnswers`	No
`meetingFormat`	No	Copy the value from preview_booking unchanged.
`confirmationToken`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`message`	No
`nextCursor`	No
`nextOffset`	No
`syncStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / meetingFormat

Added value: +{
+  "description": "Copy the value from preview_booking unchanged.",
+  "maxLength": 1000,
+  "type": "string"
+}

Changed21 schema fields changedSep 13, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / confirmationToken

Added value: +{
+  "maxLength": 1000,
+  "type": "string"
+}

addedInput schema / properties / confirmed

Added value: +{
+  "const": true,
+  "type": "boolean"
+}

addedInput schema / properties / email / maxLength
```
Added value: +320
```
removedInput schema / properties / email / minLength
```
Removed value: -1
```
addedInput schema / properties / fieldAnswers / additionalProperties / maxLength
```
Added value: +2000
```

removedInput schema / properties / fieldAnswers / description

Removed value: -"Answers to the page's requiredFields, keyed by label."

addedInput schema / properties / fieldAnswers / propertyNames / maxLength
```
Added value: +60
```
addedInput schema / properties / fieldAnswers / propertyNames / minLength
```
Added value: +1
```

removedInput schema / properties / meetingType / description

Removed value: -"Required when the page offers more than one option."

addedInput schema / properties / name / maxLength
```
Added value: +200
```

removedInput schema / properties / purpose / description

Removed value: -"One line on why the guest wants to meet."

addedInput schema / properties / purpose / maxLength
```
Added value: +2000
```

changedInput schema / properties / requestId / description

Previous value: -"Reuse this ID when retrying the same confirmed booking request."New value: +"Reuse the ID returned by preview_booking for retries."

removedInput schema / properties / slotId / minLength
```
Removed value: -1
```

addedInput schema / properties / slotId / pattern

Added value: +"^s_\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}Z$"

addedInput schema / properties / slug / maxLength
```
Added value: +2048
```

removedInput schema / properties / timezone / description

Removed value: -"Guest IANA timezone; defaults to the host's."

addedInput schema / properties / timezone / maxLength
```
Added value: +100
```

changedInput schema / required

Previous value: -[
-  "slug",
-  "name",
-  "email",
-  "slotId"
-]New value: +[
+  "slug",
+  "name",
+  "email",
+  "slotId",
+  "confirmationToken",
+  "confirmed"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "nextCursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nextOffset": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "syncStatus": {
+      "enum": [
+        "pending",
+        "ready",
+        "attention"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / requestId

Added value: +{
+  "description": "Reuse this ID when retrying the same confirmed booking request.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical runtime behavior: paid meetings are not booked until payment succeeds, the secure payment URL must be shown without claiming confirmation, and notifications must not be considered delivered until syncStatus is ready. This adds substantial value beyond readOnly/destructive hints.

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?

Four dense sentences, all earning their place: outcome, payment caveat, precondition, and retry/notification constraints. The most important usage rule is front-loaded, and there is no filler or repetition of schema details.

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 12-parameter tool with an output schema, the description covers the essential operational context: when to call, what to copy, how to handle paid bookings, retries, and sync status. The output schema handles return-value specifics, so nothing needed for correct invocation is materially missing.

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 description coverage is very low (17%), but the description compensates with crucial guidance: copy the preview's booking fields and confirmationToken unchanged, and reuse requestId and confirmationToken on retries. It does not individually explain every parameter, but the copy-unmodified instruction covers most booking fields and targets the highest-risk semantics.

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?

The description states a specific verb and resource: it creates a free booking or returns PAYMENT_REQUIRED for paid ones. It clearly distinguishes itself from siblings by tying directly to preview_booking approval, so an agent can tell book_meeting apart from preview, reschedule, and cancel.

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?

The description gives an explicit precondition: only call after the guest explicitly approves preview_booking. It also clarifies the paid-meeting flow, retry behavior, and when not to claim confirmation or notification delivery, leaving little room for misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Yoya Booking 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.

Resources

Need Help?