Feature: Add calendar tools#349
Open
seanogdev wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The Go SDK gained calendar support in Teamwork/twapi-go-sdk#46 but it was never wired into the MCP. This PR adds three calendar tools to the
twprojects-timetoolset, covering the new v3 calendars feature including time blocking.twprojects-list_calendarslists calendars, including theblocked_timecalendar that holds the account's time-blocking eventstwprojects-list_calendar_eventslists events from a calendar with date range filters and cursor pagination. When verbose it sideloads users, projects, tasks and timelogs so timeblocks resolve to their linked entities without extra callstwprojects-create_calendarcreatesevent,blocked_timeorholidaycalendars. Thegoogleandoutlooktypes are deliberately excluded since those only come into existence via the sync integrationsCalendar deletion is intentionally not exposed. Calendars are user-scoped in the product and deleting one (especially the account-wide
blocked_timecalendar) isn't an operation an AI agent should be making, so we only expose the read and create side.Both list tools follow the
list_*contract:verboseparameter, raw body streaming viaExecuteRaw, a sparse field set whenverbose=falseandWithOptionalFieldson the output schema.The SDK only supports reading events for now, so there's no create/update tool for events or timeblocks yet. Once that lands in the SDK we can add the write side here.
Type of Change
Testing
go test -v ./...)Checklist