Files
PaperClipAI/server
DottaandClaude Opus 5.5 f61b919701 feat(google-workspace): REST-backed Docs and Slides tools; mark Calendar update_event destructive (#22029)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work
> - The Google Workspace connector gives agents Google tools through the
tool gateway
> - Google's hosted Workspace MCP servers are a Developer Preview, so
Paperclip launches on its own tools over Google's REST APIs, in
`server/src/google-workspace-rest-tools/`
> - Gmail and Calendar are done there; Docs and Slides have no tools yet
> - This pull request adds `read_doc`, `update_doc`, `read_presentation`
and `update_presentation` with the same names and inputs as Google's MCP
tools
> - The benefit is that the Docs and Slides services can switch to
`paperclip_rest` once their API is enabled, and reviewers see a full
document in Paperclip

## Linked Issues or Issue Description

**Subsystem affected**
Google Workspace REST tool set
(`server/src/google-workspace-rest-tools/`), Docs and Slides services.

**Problem or motivation**
The REST tool set has no Docs or Slides tools. The allowlist
(`toolScopes.docs`, `toolScopes.slides`) names two tools for each
service. A service cannot switch to `paperclip_rest` until all of its
allowlisted tools exist.

**Proposed solution**
Add the four tools in new `docs/` and `slides/` folders. Each tool makes
exactly one REST call. The read tools return the whole file as
Markdown-style text plus an index structure for edits. The update tools
post `batchUpdate` requests in order and require the revision ID that
the caller read.

**Alternatives considered**
Return the raw `documents.get` JSON. It is 10 to 20 times larger than
the text, so ordinary documents go over the result size limit, and it is
hard to compare with Google Docs. Reorder edit requests by index. That
changes what dependent requests do, and Google's tool does not do it.

Refs #22000, #22014, #22017

## What Changed

- `docs/`: `read_doc` (`documents.get` with `includeTabsContent=true`)
and `update_doc` (`documents.batchUpdate`), a renderer for every tab,
child tab, heading, list (real numbering), table, link, header, footer,
footnote, chip, suggestion and comment, and an index structure where
each paragraph's `text.length` equals `endIndex - startIndex`.
- `slides/`: `read_presentation` (`presentations.get`; with `fields` it
returns Google's resource as is) and `update_presentation`
(`presentations.batchUpdate`), a renderer for every slide's text,
tables, groups, media and speaker notes.
- `documents-shared.ts`: the 250,000-byte limit on the final serialized
result (an error, never a cut-short result), the revision-conflict
error, comment rendering, and argument checks.
- Update tools require `writeControl.requiredRevisionId` and refuse
`targetRevisionId`. A revision conflict returns "nothing was changed;
read it again". Writes are never retried.
- `google-http.ts`: allows `docs.googleapis.com` only under
`/v1/documents/` and `slides.googleapis.com` only under
`/v1/presentations/`.
- `tools.ts`, `probe.ts`: register the services. Docs and Slides have no
network probe, because every read needs a file ID.
- Update tools accept only a closed list of batch request kinds
(`docs/request-kinds.ts`, `slides/request-kinds.ts`). Kinds and forms
that read another file are refused by name: `insertRichLink`, the Sheets
chart kinds, `importSlides`, `createAudio`, Drive videos, and images
from Drive or Docs links. Unknown kinds are refused too.
- `read_doc` always requests `SUGGESTIONS_INLINE` and falls back to an
explicit `PREVIEW_WITHOUT_SUGGESTIONS` read for view-only users; the
result says which view it used.
- Tables with merged cells are placed on the full grid; covered cells
read `(merged left)` or `(merged up)`.
- Revision conflicts are recognized from Google's `error.status` and
`error.details` first, with the message as a fallback.
- Annotations: `update_doc` and `update_presentation` are destructive
and not idempotent. **Calendar `update_event` is now also marked
destructive** (it overwrites fields, removes attendees and replaces
reminders). Google's references mark both non-destructive; the README
records this.
- `README.md`: endpoint and scope table with Google's documentation
links, the result format, what cannot be shown, update order and
revision rules, and every difference from Google's tools.

## Verification

- `cd server && npx vitest run src/google-workspace-rest-tools`: 33
files, 573 tests pass (169 new in `docs/` and `slides/`, plus host,
probe and allowlist tests).
- `cd server && pnpm typecheck`: passes.
- `pnpm verify`: exit 2 (README is a broad input), so required CI
supplies broad coverage.
- `src/services/google-workspace-rest-dispatch.test.ts` fails the same
way on `master` (it still expects Gmail to be incomplete after #22014).
This PR does not touch it.

## Risks

- Low risk. Nothing calls these tools until the Docs or Slides transport
is set to `paperclip_rest`; both stay `google_mcp`.
- The inner format of `content` differs from Google's tool, which Google
does not publish. The README lists this.
- Revision-conflict detection matches Google's 400 message on
"revision". Any 400 rejects the whole batch, so nothing changes in
either case.

## Model Used

- Claude Opus 5.5 (`claude-opus-5-5`), Anthropic, in Claude Code with
tool use and code execution.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 17:28:13 +00:00
..