Skip to content

feat(google-workspace): add per-service prompts for agents#419

Merged
JonasJesus42 merged 2 commits into
mainfrom
JonasJesus42/google-workspace-prompts
May 5, 2026
Merged

feat(google-workspace): add per-service prompts for agents#419
JonasJesus42 merged 2 commits into
mainfrom
JonasJesus42/google-workspace-prompts

Conversation

@JonasJesus42
Copy link
Copy Markdown
Contributor

@JonasJesus42 JonasJesus42 commented May 5, 2026

Summary

Adds curated MCP prompts to google-workspace, mirroring the pattern HyperDX already uses (server/prompts.ts exposed via prompts/list / prompts/get). An agent can pull only the relevant guide on demand instead of cramming every tool description into its system prompt.

Six prompts:

  • GOOGLE_WORKSPACE_AGENT_GUIDE — entry point. Lists the 5 services, the tool prefix convention, time/timezone rules, destructive-action rules, pagination, and re-auth handling.
  • GOOGLE_WORKSPACE_CALENDAR_GUIDE — Calendar tool selection, the primary calendar convention, scheduling/free-time/reschedule workflows, and recurring-event pitfalls.
  • GOOGLE_WORKSPACE_GMAIL_GUIDE — Gmail search syntax (from:, is:unread, newer_than:7d, after:2026/04/01), thread vs. message ops, system label IDs (INBOX, SENT, …), and the drafts-only caveat (this MCP has no send_message for mail).
  • GOOGLE_WORKSPACE_DRIVE_GUIDE — Drive structured query syntax (name contains, '<folderId>' in parents), MIME types for Docs/Sheets/Slides, read_file_content vs. download_file_content, base64 caveats.
  • GOOGLE_WORKSPACE_CHAT_GUIDE — Spaces vs. DMs, threading, send-message confirmation pattern.
  • GOOGLE_WORKSPACE_PEOPLE_GUIDE — directory (Workspace-only) vs. personal contacts, get_user_profile as the "who am I" shortcut.

Each prompt is hand-written from the actual tool catalog (see TOOLS.md) — describes what tools exist, when to call which one, and what to watch out for.

Why hand-written instead of generated?

The auto-generated TOOLS.md and the per-tool description fields already cover what each tool does. The prompts cover how to use them together — workflow guidance that doesn't come for free from upstream metadata. They're stable across Google's catalog changes (re-running generate-tools doesn't touch them).

Test plan

  • bun run check — clean (tsc --noEmit)
  • bun run build — bundles 2.13 MB / 401 modules
  • bun scripts/check.ts google-workspace — ✅ passed
  • After deploy + auth: prompts/list returns 6 entries
  • prompts/get GOOGLE_WORKSPACE_GMAIL_GUIDE returns the markdown body
  • Spot-check that the agent picks up the right prompt when handed an ambiguous Gmail / Drive / Calendar question

🤖 Generated with Claude Code


Summary by cubic

Add curated per‑service MCP guides and user workflow templates to google-workspace, exposed via prompts/list and prompts/get. Agents can pull focused docs on demand, and users can launch common tasks without bloating system prompts.

  • New Features
    • Added six per‑service guides (GOOGLE_WORKSPACE_*_GUIDE; Gmail notes drafts‑only) and 11 user templates across Calendar, Gmail, Drive, Chat, and People (e.g., morning_briefing, find_meeting_time, draft_reply, find_files).
    • Registered prompts in runtime (server/main.ts), added server/prompts.ts, and updated README.md with the lists and source path.

Written for commit 36a34f0. Summary will update on new commits.

JonasJesus42 and others added 2 commits May 5, 2026 06:12
Mirrors the pattern HyperDX uses (`server/prompts.ts` exposed via
`prompts/list` and `prompts/get`) so an agent can pull just the relevant
guide on demand instead of stuffing every tool description into its
system prompt.

Adds six prompts:

- GOOGLE_WORKSPACE_AGENT_GUIDE — entry point covering all 5 services,
  tool naming, time/timezone, destructive actions, pagination, re-auth.
- GOOGLE_WORKSPACE_CALENDAR_GUIDE — primary calendar convention,
  scheduling workflows, recurring-event pitfalls.
- GOOGLE_WORKSPACE_GMAIL_GUIDE — Gmail search syntax, thread vs message,
  system-label IDs, and the drafts-only caveat (this MCP cannot send mail).
- GOOGLE_WORKSPACE_DRIVE_GUIDE — Drive structured query syntax, MIME
  types, content vs metadata vs permissions, base64 download note.
- GOOGLE_WORKSPACE_CHAT_GUIDE — Spaces vs DMs, threading, send-message
  confirmation pattern.
- GOOGLE_WORKSPACE_PEOPLE_GUIDE — directory (Workspace-only) vs personal
  contacts, get_user_profile shortcut.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…rkflows

Adds 11 prompt templates (with arguments) the user can pick from the MCP
prompt menu — slash-command-style entries that drive the agent through
common day-to-day tasks across the 5 wrapped services:

Cross-service:
- morning_briefing — calendar + important unread + recent chat
- prep_for_meeting — attendees, last emails with them, shared docs

Calendar:
- whats_on_calendar — flexible time window
- find_meeting_time — multi-attendee free/busy
- block_focus_time — reserve a private block, confirms first

Gmail:
- inbox_triage — classify Reply/FYI/Action/Noise
- draft_reply — find thread + create draft (user must Send)

Drive:
- find_files — natural-language → structured query
- summarize_doc — find by name + read content + summarize

Chat:
- catch_up_chat — Decisions / Action items / Open threads / FYI

People:
- find_person — directory + personal contacts

Each template is a single user message that orchestrates the right tools.
Destructive operations (create event, draft reply, send chat) explicitly
ask the agent to confirm before invoking.

Existing agent guides are kept under the same export, separated by
section comments.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@JonasJesus42 JonasJesus42 merged commit 33c9d72 into main May 5, 2026
2 checks passed
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