Page Lemon

Change a booking

edit_booking

Destructive

Changes one booking: customer details, or start (and resource) to move it. A class_id (cl_…) as item_id: start moves the class; waitlist closes or re-opens it. A move or a change that emails someone asks first (confirm_token); force: true books a clash.

Input Schema

Name	Required	Description
`name`	No
`site`	Yes
`email`	No
`force`	No
`notes`	No
`party`	No
`phone`	No
`start`	No	New local time, e.g. "2026-10-15T14:00"
`answers`	No	{question id: answer} ("" removes one)
`item_id`	Yes
`message`	No	A note for the customer
`resource`	No	With start: staff or room
`waitlist`	No	Class time or wl_ entry: close (bookings stay; those waiting are emailed) or re-open
`plugin_id`	No	Default: booking page
`confirm_token`	No
`notify_customer`	No	Email the customer (default true)

Output Schema

Name	Required	Description	Default
`bookings`	No
`agent_message`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- addedOutput schema / properties / agent_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / bookings
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedOct 26, 2026
- removedInput schema / properties / item_id / description
```
Removed value: -"From get_lists"
```

Changed1 schema field changedOct 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "confirm_token": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 24, 2026
- removedInput schema / properties / confirm_token / description
```
Removed value: -"After the user's yes"
```
- changedInput schema / properties / plugin_id / description
```
Previous value: -"Default: the booking page"New value: +"Default: booking page"
```
Changed1 schema field changedOct 22, 2026
- removedInput schema / properties / site / description
```
Removed value: -"Site name"
```

Changed18 schema fields changedOct 21, 2026

removedInput schema / additionalProperties
```
Removed value: -{}
```
removedInput schema / properties / answers / additionalProperties
```
Removed value: -{
-  "maxLength": 500,
-  "type": "string"
-}
```

changedInput schema / properties / answers / description

Previous value: -"{question id: answer} for the settings' questions (\"\" removes one)"New value: +"{question id: answer} (\"\" removes one)"

changedInput schema / properties / confirm_token / description

Previous value: -"From the first call, after the user's yes"New value: +"After the user's yes"

removedInput schema / properties / email / maxLength
```
Removed value: -254
```
removedInput schema / properties / force / description
```
Removed value: -"Book even if it clashes"
```
removedInput schema / properties / message / maxLength
```
Removed value: -500
```
removedInput schema / properties / name / maxLength
```
Removed value: -100
```
removedInput schema / properties / notes / maxLength
```
Removed value: -1000
```

changedInput schema / properties / notify_customer / description

Previous value: -"Email the customer (default true when there is an email)"New value: +"Email the customer (default true)"

removedInput schema / properties / phone / maxLength
```
Removed value: -40
```

changedInput schema / properties / plugin_id / description

Previous value: -"Default: the site's booking page"New value: +"Default: the booking page"

changedInput schema / properties / resource / description

Previous value: -"With start: staff or room id or name"New value: +"With start: staff or room"

removedInput schema / properties / resource / maxLength
```
Removed value: -60
```

changedInput schema / properties / site / description

Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"

changedInput schema / properties / start / description

Previous value: -"A new time: local \"2026-10-15T14:00\" (booking time zone)"New value: +"New local time, e.g. \"2026-10-15T14:00\""

changedInput schema / properties / waitlist / description

Previous value: -"A class time (cl_…) or wl_ entry: close its waitlist (bookings stay; the people waiting are emailed) or re-open it"New value: +"Class time or wl_ entry: close (bookings stay; those waiting are emailed) or re-open"

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed5 schema fields changedOct 20, 2026

addedInput schema / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / item_id / description

Previous value: -"From list_plugin_data"New value: +"From get_lists"

changedInput schema / properties / plugin_id / description

Previous value: -"From list_plugins"New value: +"Default: the site's booking page"

addedInput schema / properties / waitlist

Added value: +{
+  "description": "A class time (cl_…) or wl_ entry: close its waitlist (bookings stay; the people waiting are emailed) or re-open it",
+  "enum": [
+    "closed",
+    "open"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "site",
-  "plugin_id",
-  "item_id"
-]New value: +[
+  "site",
+  "item_id"
+]

AddedOct 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true. On top of that the description discloses the two-step confirm_token confirmation flow for moves/emailing changes and the clash-override behavior of force:true, which are meaningful behavioral facts not in the annotations or schema.

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?

Three front-loaded sentences covering the main purpose first, then edge cases. Extremely dense but nearly every clause carries information; only the compressed phrasing of the confirm_token sentence borders on cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and annotations are rich, lowering the burden, and the description handles the tricky interactions. But for a 16-parameter mutation tool with 44% schema coverage, several parameters still lack any documented semantics, leaving the definition short of complete.

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 only 44%, so the description must compensate. It adds real meaning for item_id's cl_ convention, the start+resource pairing, confirm_token, and force, but leaves customer-detail fields (name, email, phone, notes, party, site) unexplained, so compensation is partial.

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 ('Changes one booking') and enumerates what can change: customer details, or start+resource to move. It also disambiguates item_id (a cl_ prefix means a class). Sibling routing (vs add_booking, cancel_booking, set_booking_outcome) is implied but never named.

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?

The description gives invocation-level guidance for tricky parameters ('A move or a change that emails someone asks first (confirm_token); force: true books a clash'), which is real when-to-use context. However, it does not state when to choose this over cancel_booking or set_booking_outcome, leaving the main routing decision to inference.

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

All Page Lemon tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?