MCP tool design: should rescheduling be one tool call, or cancel plus book?
Normal_Succotash_520 · reddit · 2026-09-18
A developer building a scheduling MCP integration asks how the agent-facing reschedule operation should promise behavior: move a Tuesday appointment to Thursday via cancel + book, or a single reschedule tool?
- Cancel first: a failed booking leaves the user with nothing
- Book first: a failed cancellation leaves two appointments and duplicate notifications
- Naming it one operation doesn't make the underlying calendar calls atomic; a timeout after creating the replacement makes retries ambiguous
They ask developers exposing calendar/booking APIs via MCP whether they reserve slots, update existing events, or run compensating actions — and what to return to the agent when partial state can't be resolved, especially when the provider lacks transactional support.
More from coding & agent
- Kimi Agent Swarm tested in the cloud: 16-hour autonomous training run with self-recovery — solyarisoftware · 2026-09-18
- Open-source PR Review Lab spins up sandboxes to compare GPT 5.6 Luna vs Jev reviewers — aniketmaurya · 2026-09-18
- One customer drives $10k MRR as indie AI agent product doubles September revenue — tibo_maker · 2026-09-18
- The real agent security weak point is over-privileged access, not faster exploits — code_star · 2026-09-18
- Solo dev ships hosted CVE + CISA KEV + EPSS MCP server, no API key needed — sartomiki · 2026-09-18
- Agent runs autonomously for 1.5 days to train a dexterous-hand pen-spinning RL policy — SatelliteNetSec · 2026-09-18