Repository navigation
Description
The Calendar CLI supports listing events across pages, but the MCP calendar_events input schema has no continuation-token argument. A caller reaching the first page limit cannot continue the same Calendar query through that tool.
At 9e972923686f69c75f5ff21c4afaf5c26f3342ec, the schema exposes calendar/time-window/query selectors and max (up to 250), but no page-token input. The argument builder does not map one to the CLI.
Expected interaction: request a bounded page for one calendar and time window, then pass the response's continuation token with the same selectors to retrieve the next page. This avoids repeatedly subdividing a busy time window merely to enumerate its events.
Would you be open to exposing the existing CLI continuation mechanism as an optional MCP input? We have a downstream implementation and would follow your preferred naming/interface.
Credential-free source check
From a checkout at the revision above:
python3 - <<'PYTHON'
from pathlib import Path
s = Path("internal/cmd/mcp_tools.go").read_text()
b = s.split("func mcpCalendarEventsTool()", 1)[1].split("\nfunc ", 1)[0]
print("MCP page input:", 'WithString("page"' in b)
print("MCP page forwarding:", 'req.GetString("page"' in b)
s = Path("internal/cmd/calendar_events_cmds.go").read_text()
print("CLI page flag:", 'name:"page"' in s)
PYTHONObserved: MCP page input: False, MCP page forwarding: False, CLI page flag: True. This verifies the interface gap by source inspection, not a live multi-page mailbox/calendar read. No credentials or Google API requests were used.
Investigated and reproduced with AI assistance (the Astrarch agent team); the reproduction was verified on a real host.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
clawsweeper commentedon Oct 26, 2026
Codex review: this still needs some work.
Summary
This issue identifies a missing MCP capability on current main; the related open PR adds paginated Calendar search but leaves calendar_events unchanged.
Reproducibility: Source confirms the absent schema input and argument mapping while the CLI accepts and returns page tokens; no live multi-page Calendar call or tests were run.
Maintainer decision needed
Next step
Choose the optional page interface and coordinate its scope with #1181 before implementation.
Review details
Best possible solution:
Provide bounded continuation through calendar_events using the existing CLI page mechanism.
Do we have a high-confidence way to reproduce the issue?
Source confirms the absent schema input and argument mapping while the CLI accepts and returns page tokens; no live multi-page Calendar call or tests were run.
Is this the best way to solve the issue?
An optional page input is a narrow extension of the typed tool and preserves bounded reads without introducing automatic traversal or broader permissions.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning medium; reviewed against 9e972923686f.
Label changes
Label changes:
P2: A focused MCP capability gap limits busy-calendar enumeration without evidence of an urgent regression.impact:ux-friction: MCP callers must subdivide time windows or use the CLI to continue an otherwise valid event listing.issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.clawsweeper:source-repro: Current issue advisory state selects this label.clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.clawsweeper:fix-shape-clear: Current issue advisory state selects this label.clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.clawsweeper:needs-product-decision: Current issue advisory state selects this label.Label justifications:
P2: A focused MCP capability gap limits busy-calendar enumeration without evidence of an urgent regression.impact:ux-friction: MCP callers must subdivide time windows or use the CLI to continue an otherwise valid event listing.Evidence reviewed
Acceptance criteria:
What I checked:
internal/cmd/mcp_tools.go:244, 9e972923686f)internal/cmd/mcp.go:118, 9e972923686f)internal/cmd/calendar_list.go:30, 9e972923686f)internal/cmd/calendar_events_test.go:17, 9e972923686f)internal/cmd/mcp_calendar.go, 3a6a5e0fb35c)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.Reviewed October 26, 2026, 3:41 PM ET / 19:41 UTC.
steipete commentedon Oct 27, 2026
The existing calendar_events MCP tool now accepts optional page input and forwards the opaque continuation token to the bounded CLI event list. A two-page MCP-to-CLI synthetic API regression verifies token forwarding with the same calendar, window, query, and limit.
Fixed by #1273, merged as 8c5c062. The regression failed on the previous main and passes with the fix. Focused tests, the remote gate, and exact-head CI passed. Independent review found no actionable P0–P2 issues. Thanks @pkyIntelligence.
fix: preserve Calendar clears and bounded MCP continuation (openclaw#…