Capable

Reschedule meeting

reschedule_meeting

DestructiveIdempotent

Move an ALREADY-CONFIRMED (booked) meeting to a new time, in place. The existing calendar event is patched to the new time — SAME event, SAME video call link, SAME attendees, same calendar invite (no new invite, no new link). The invitee gets a "your meeting moved to {new time}" email. This is the answer to "move my 2pm to Thursday" / "push the Acme call an hour."

Use this ONLY for a confirmed meeting. For a meeting still awaiting the invitee's pick (not yet booked), there's nothing to move — cancel it and propose new times instead (the tool returns a clear not_confirmed error in that case).

new_start is an ISO 8601 instant. Get a valid time from find_times first when you need to check the host's calendar — but you can also pass a specific time the user named. Duration is preserved from the current booking unless you pass new_duration_min. The new time is freebusy-checked against every host (the move is refused if a host is busy then); the host's own saved workday / buffers / minimum-notice are NOT re-applied — the host is the authority over their own meeting.

Confirm the new time with the user before calling (it edits a live calendar event and emails the invitee). Returns the meeting's full state + the new when-label + the video call link. Reschedule is host-driven only; the invitee doesn't re-pick.

When to use: Move an already-booked meeting to a new time without re-doing anything. The same calendar event is edited in place — same video call link, same attendees, same invite — and the invitee gets a "moved to {new time}" note. Only for confirmed meetings; for one still awaiting a pick, cancel and propose again instead. The new time is freebusy-checked against every host.

Example: Move my 2pm with Sara to Thursday at the same time.

Input Schema

TableJSON Schema

Name	Required	Description
`new_start`	Yes	ISO 8601 start of the new time (e.g. a find_times slot's starts_at, or a specific time the user named). Must be in the future and different from the current start.
`meeting_id`	Yes	The confirmed meeting's id, from search_records or get_record.
`new_duration_min`	No	Optional new duration in minutes. Omit to keep the meeting's current length.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`note`	No
`slots`	No
`meeting`	No
`guidance`	No
`meet_link`	No
`timed_out`	No
`meeting_id`	No
`rescheduled`	No
`new_when_label`	No
`co_host_repair_needed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Far exceeds the annotations: discloses that the same event/link/invite is preserved, that an invitee email is sent, that the new time is freebusy-checked against every host and refused if busy, that host workday/buffers/min-notice are NOT re-applied, and that the user should confirm first since it edits a live event. This gives an agent the full mutation side-effect picture consistent with destructiveHint=true.

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

Conciseness3/5

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

Front-loaded and readable, but the closing 'When to use' block largely duplicates the opening paragraphs (same-event-in-place, invitee note, confirmed-only, freebusy check), so a meaningful chunk of text does not earn its place.

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 mutation tool with an output schema, the description covers everything an agent needs: preconditions, side effects, validation behavior, and the routing decision versus siblings. Nothing relevant is left unspecified.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: new_start is an ISO 8601 instant obtainable from find_times or a user-named time, and duration is preserved unless new_duration_min is passed. It doesn't restate the schema, it enriches the decision logic around the parameters.

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 and resource with scope: 'Move an ALREADY-CONFIRMED (booked) meeting to a new time, in place', and immediately clarifies it patches the SAME event with the SAME link and attendees. This distinguishes it cleanly from cancel_meeting, propose_meeting, and find_times.

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?

Explicitly says 'Use this ONLY for a confirmed meeting' and names the correct alternative path for unconfirmed meetings ('cancel it and propose new times instead'), plus the not_confirmed error behavior. It even supplies trigger phrasing ('move my 2pm to Thursday').

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

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