MightyAutomation

Reschedule an appointment

reschedule_appointment

Destructive

Move an appointment to a new start time (and optionally a new length). Ids come from list_appointments. CRM calendar only — no attendee email. Appointments synced to Google Calendar or booked through a scheduling link return manage_in_app: reschedule those in the Sales Calendar.

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": {
      "appointment_id": "<appointment_id>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "reschedule_appointment"
  }
}

Input Schema

Name	Required	Description
`scheduled_at`	Yes	New ISO 8601 start time with an offset.
`appointment_id`	Yes	Appointment id (uuid) from list_appointments.
`duration_minutes`	No	New length in minutes, 5-480 (default: unchanged).

Output Schema

Name	Required	Description
`ok`	No
`error`	No	Present only when ok is false.
`message`	No
`appointment`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Although annotations already declare this a destructive operation, the description adds vital operational context: the source of IDs, the specific calendar it operates on (CRM only), and instructions for external systems. This significantly increases the agent's confidence in using the tool correctly.

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 dense but highly informative. It places the primary action and constraints at the front, though the final clause explaining external calendar management is slightly complex.

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?

Given the complexity of handling synced vs. native CRM appointments, the description is highly complete. It defines the scope, constraints, necessary inputs, and exception handling without needing to detail output values since an output schema exists.

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?

The input schema has 100% description coverage, meaning the structured data already defines all parameter meanings. The text does not add semantic meaning beyond what the schema provides regarding time formats or minute ranges, thus falling back to the baseline score of 3.

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 clearly states the verb ('Move'), the resource ('appointment'), and the strict operational scope ('CRM calendar only'). It also preemptively guides the agent on the required ID source ('list_appointments').

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 provides excellent usage constraints, detailing that attendee emails are unavailable, and crucially, it specifies that external calendars (Google Calendar/Sales Calendar link) require management via a different interface, making the boundary clear.

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

All MightyAutomation 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?