FavCRM

reschedule_booking

Move or reassign a single-service booking to a new date, time, staff member, resource or schedule slot. Multi-service appointments must be handled in the merchant dashboard. Runs conflict, capacity and rebooking-policy checks, enforces actor permissions and outlet access, syncs the booking calendar, and returns the updated booking.

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": {
      "bookingId": "<bookingId>"
    },
    "name": "reschedule_booking"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Replace the booking notes
`endTime`	No	New end time in HH:MM format
`staffId`	No	Reassign to the staff userId returned by list_staff; null clears the assignment
`bookingId`	Yes	The booking ID to reschedule
`startTime`	No	New start time in HH:MM format
`resourceId`	No	Assign this resource ID; null clears the assignment
`scheduleId`	No	Target schedule slot ID when moving between schedule windows
`bookingDate`	No	New date in YYYY-MM-DD format

Output Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare the mutation/safety profile (readOnly false, destructive false, idempotent false), and the description layers on substantial behavioral context: conflict, capacity and rebooking-policy validation, actor permission and outlet access enforcement, calendar sync, and an updated-booking return. That tells the agent what can fail and why, which the annotations never do.

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?

Two sentences, no filler, and the core action is front-loaded before the exclusion and the behavioral checks. Every clause carries distinct information — scope, restriction, then validation/side effects.

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?

For an 8-parameter mutation with an output schema and full schema coverage, the description covers scope, exclusions, validation, permissions and the return payload, which is nearly everything an agent needs. The remaining gap is update semantics — whether unspecified fields keep their values — which matters for a partial-update reschedule call.

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 every parameter already carries its own description and the baseline is 3. The description only restates the changeable dimensions already visible in the schema; it adds no new constraint such as partial-update semantics (whether omitted fields are preserved) or interaction between startTime/endTime and scheduleId.

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 ('Move or reassign') against a specific resource ('a single-service booking') and enumerates the dimensions that can change (date, time, staff, resource, schedule slot). It also scopes itself against non-single-service bookings, so an agent can separate it from cancel_booking and create_booking without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear use case plus an explicit exclusion: multi-service appointments must go to the merchant dashboard. That is real routing guidance. It does not name a sibling tool for the excluded case or cover when to cancel-and-recreate instead of reschedule, keeping it out of the 5 tier.

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

All FavCRM 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.