Skip to main content
Glama
HuntsDesk

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

manage_focus_time

Create, list, update, or delete Focus Time events that auto-decline conflicting invites and set chat to Do Not Disturb.

Instructions

Create, list, update, or delete Focus Time events.

Focus Time is a special event type that auto-declines conflicting invitations and (by default) sets Google Chat to Do Not Disturb for the duration. Lives on the primary calendar only. For regular events use manage_event; for OOO use manage_out_of_office. Side effects: mutating actions may auto-decline existing/incoming invites and flip chat presence. Requires the calendar.events OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
actionYes"create", "list", "update", or "delete". Case-insensitive.
start_timeNoStart date/time. "YYYY-MM-DD" auto-converts to midnight; RFC3339 works for partial days.
end_timeNoEnd (exclusive). For a full day on Apr 5 pass start="2026-04-05", end="2026-04-06".
summaryNoDisplay label. Defaults to "Focus Time".
descriptionNoOptional body text for context.
auto_decline_modeNo"declineAllConflictingInvitations" (default), "declineOnlyNewConflictingInvitations", or "declineNone".
decline_messageNoBody of auto-decline replies.
chat_statusNo"doNotDisturb" (default) or "available".
recurrenceNoRFC5545 rules, e.g. ["RRULE:FREQ=WEEKLY;COUNT=10"].
timezoneNoIANA zone like "America/New_York". Required when start/end are date-only or lack a UTC offset.
time_minNoList-action range start. Defaults to now.
time_maxNoList-action range end.
max_resultsNoList-action cap. Default 10.
event_idNoEvent ID. Required for update and delete.
calendar_idNoDefault "primary". Focus Time lives on primary calendars only — pass "primary" or the user's primary email.primary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed16 schema fields changedv1.0.0
    • changedInput schema / properties / action / description
      Previous value: -"Action to perform - \"create\", \"list\", \"update\", or \"delete\"."New value: +"\"create\", \"list\", \"update\", or \"delete\". Case-insensitive."
    • changedInput schema / properties / auto_decline_mode / description
      Previous value: -"How to handle conflicting invitations. One of: \"declineAllConflictingInvitations\" (default), \"declineOnlyNewConflictingInvitations\", \"declineNone\"."New value: +"\"declineAllConflictingInvitations\" (default),\n\"declineOnlyNewConflictingInvitations\", or \"declineNone\"."
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID. Defaults to 'primary'. Focus Time status events live on primary calendars, so use 'primary' or a user's primary calendar ID/email rather than a secondary calendar ID."New value: +"Default \"primary\". Focus Time lives on primary\ncalendars only — pass \"primary\" or the user's primary email."
    • changedInput schema / properties / chat_status / description
      Previous value: -"Google Chat status during the focus time. Supports \"doNotDisturb\" (default) and \"available\"."New value: +"\"doNotDisturb\" (default) or \"available\"."
    • changedInput schema / properties / decline_message / description
      Previous value: -"Message included when auto-declining invitations."New value: +"Body of auto-decline replies."
    • changedInput schema / properties / description / description
      Previous value: -"Event description. Useful for adding context about what the focus time is for."New value: +"Optional body text for context."
    • changedInput schema / properties / end_time / description
      Previous value: -"End date/time (exclusive). Same format as start_time. For a single full day on April 5, use start_time='2026-04-05' and end_time='2026-04-06'. Required for create."New value: +"End (exclusive). For a full day on Apr 5 pass\nstart=\"2026-04-05\", end=\"2026-04-06\"."
    • changedInput schema / properties / event_id / description
      Previous value: -"Event ID. Required for \"update\" and \"delete\" actions."New value: +"Event ID. Required for update and delete."
    • changedInput schema / properties / max_results / description
      Previous value: -"For \"list\" action: maximum events to return. Defaults to 10."New value: +"List-action cap. Default 10."
    • changedInput schema / properties / recurrence / description
      Previous value: -"RFC5545 recurrence rules for a recurring Focus Time series, e.g. [\"RRULE:FREQ=WEEKLY;COUNT=10\"]."New value: +"RFC5545 rules, e.g. [\"RRULE:FREQ=WEEKLY;COUNT=10\"]."
    • changedInput schema / properties / start_time / description
      Previous value: -"Start date/time. Use 'YYYY-MM-DD' for full-day or RFC3339 for partial-day (e.g., '2024-04-05T09:00:00Z'). Date-only values are auto-converted to dateTime (midnight-to-midnight). Required for create."New value: +"Start date/time. \"YYYY-MM-DD\" auto-converts to\nmidnight; RFC3339 works for partial days."
    • changedInput schema / properties / summary / description
      Previous value: -"Display text on the calendar. Defaults to \"Focus Time\"."New value: +"Display label. Defaults to \"Focus Time\"."
    • changedInput schema / properties / time_max / description
      Previous value: -"For \"list\" action: end of time range."New value: +"List-action range end."
    • changedInput schema / properties / time_min / description
      Previous value: -"For \"list\" action: start of time range. Defaults to current time. Recurring series are expanded into individual instances in the requested range."New value: +"List-action range start. Defaults to now."
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone for the event (e.g., \"America/New_York\", \"Europe/London\"). Required when using date-only values or dateTime values without an explicit UTC offset."New value: +"IANA zone like \"America/New_York\". Required when\nstart/end are date-only or lack a UTC offset."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses key behaviors: auto-declines conflicting invitations, sets Chat to Do Not Disturb by default, lives on primary calendar only, and requires 'calendar.events' scope. This is good but lacks details on error handling or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph but concise, covering purpose, usage alternatives, behaviors, and scope. It is front-loaded with the verb and resource. Slightly long but every sentence is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 16 parameters and high complexity, the description combined with the schema provides sufficient context for selection and invocation: what it does, side effects, usage guidelines, and a required scope. It could mention output schema or error scenarios but is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the Focus Time concept and side effects (auto-decline, Chat DND), which gives semantic context beyond parameter descriptions. This lifts the score to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates, lists, updates, or deletes Focus Time events, a specific event type. It distinguishes from siblings 'manage_event' and 'manage_out_of_office' by explicitly naming them and specifying what each handles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use this tool (for Focus Time events) and when to use alternatives (manage_event for regular events, manage_out_of_office for OOO). It also notes side effects and OAuth scope requirements, providing clear guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server