Skip to content

fix(mcp): require calendarName and surface 404 as actionable error#90

Merged
elgorro merged 2 commits intomainfrom
bug/mcp_calendars
Mar 6, 2026
Merged

fix(mcp): require calendarName and surface 404 as actionable error#90
elgorro merged 2 commits intomainfrom
bug/mcp_calendars

Conversation

@elgorro
Copy link
Owner

@elgorro elgorro commented Mar 6, 2026

Summary

  • Remove hardcoded 'personal' default from calendarName across all five calendar tools — this default was incorrect for Nextcloud installations that use a different calendar name
  • Surface HTTP 404 in assertCalendarSupportsEvents as a clear, actionable error message instead of letting it fall through to a raw Sabre XML response
  • Update calendarName descriptions in all tools to hint at list_calendars

Test plan

  • Call any calendar tool (create_event, list_events, etc.) with a non-existent calendar name → expect error: Calendar "X" not found. Use list_calendars to find available calendar names.
  • Verify calendarName is now required (no default) in all five calendar tools
  • npm test, npm run lint, npx prettier --check src/ all pass

🤖 Generated with Claude Code

elgorro and others added 2 commits March 6, 2026 20:14
- Remove hardcoded 'personal' default from calendarName across all five
  calendar tools — the default was wrong for many Nextcloud installations
- Throw a clear error in assertCalendarSupportsEvents on HTTP 404 so the
  AI knows to call list_calendars instead of getting a raw Sabre XML response
- Update calendarName descriptions to hint at list_calendars

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@elgorro elgorro merged commit 69fd06f into main Mar 6, 2026
3 checks passed
@elgorro elgorro deleted the bug/mcp_calendars branch March 6, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant