Skip to main content
Glama

Manage time blocks

manage_time_blocks
DestructiveIdempotent

Manage personal Google/Outlook calendar blocks with no attendees; nothing is sent. Uses booking_calendar_id (get_scheduling_settings), or Outlook's default calendar; busy unless show_as is free. create needs title, starts_at, ends_at (max 24h apart) and a fresh request_id UUID; reuse it only to retry the same block. reminder_minutes sets popup lead time; omit for calendar defaults, or use 0 on a short reminder block. list uses from/to (default next 14 days, max 62). busy returns the busy times on every calendar that blocks yours (from/to, default next 7 days, max 31; no titles), so a block can go in a free gap without the meeting card. update needs block_id and changed fields; starts_at alone preserves duration. remove deletes the block: first call asks, then requires confirm:true. Only Capable-created blocks can change.

When to use: Block focus time in a free gap, add reminders, or adjust your own blocks; use find_times for meetings with others.

Example: Block 9–11 tomorrow for writing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_time_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoList window end, default 14 days after from; busy window end, default 7 days.
fromNoList or busy window start; default now.
notesNoEvent notes; null clears them.
titleNoWhat the time is for; required for create.
actionYeslist, busy, create, update or remove.
confirmNoRequired true for remove; without it the call returns a confirmation prompt and deletes nothing.
ends_atNoISO 8601 with offset; required for create.
show_asNobusy (default) keeps booking pages and find_times off this time; free leaves it open.
block_idNoFrom list or create; required for update and remove.
starts_atNoISO 8601 with offset; required for create.
time_zoneNoIANA zone to show the block in on Google, e.g. Europe/Stockholm; Outlook shows each viewer's own zone.
request_idNoRequired for create.
reminder_minutesNoPopup lead time in minutes; null means the calendar's defaults.

Output Schema

NameRequiredDescriptionDefault
toNo
busyNo
fromNo
noteNo
blockNo
actionNo
blocksNo
statusNo
removedNo
block_idNo
truncatedNo
calendar_idNo
already_goneNo
requires_confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"list, create, update or remove."New value: +"list, busy, create, update or remove."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "create",
      -  "update",
      -  "remove"
      -]New value: +[
      +  "list",
      +  "busy",
      +  "create",
      +  "update",
      +  "remove"
      +]
    • changedInput schema / properties / from / description
      Previous value: -"List window start; default now."New value: +"List or busy window start; default now."
    • changedInput schema / properties / to / description
      Previous value: -"List window end; default 14 days after from."New value: +"List window end, default 14 days after from; busy window end, default 7 days."
    • changedOutput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "create",
      -  "update",
      -  "remove"
      -]New value: +[
      +  "list",
      +  "busy",
      +  "create",
      +  "update",
      +  "remove"
      +]
    • addedOutput schema / properties / busy
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "ends_at": {
      +        "type": "string"
      +      },
      +      "starts_at": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "starts_at",
      +      "ends_at"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Required true for remove; without it the call returns a confirmation prompt and deletes nothing.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / block_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / requires_confirm
      Added value: +{
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / time_zone / description
      Previous value: -"IANA zone to show the block in, e.g. Europe/Stockholm."New value: +"IANA zone to show the block in on Google, e.g. Europe/Stockholm; Outlook shows each viewer's own zone."
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: which calendar is written to (booking_calendar_id or Outlook default), that no invites are sent, the 24-hour duration cap, the request_id idempotency contract (reuse only to retry the same block), the two-step remove flow requiring confirm:true, and the hard restriction that only Capable-created blocks can be changed. Annotations only flag destructive/idempotent/openWorld; the description explains the actual consequences.

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?

Dense but front-loaded: scope first, then per-action rules, then a when-to-use line and a concrete example. It's long for a description, but each sentence carries a distinct constraint; minor loss for the run-on density that makes skimming harder.

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

Completeness5/5

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

For a 13-parameter, five-action mutation tool with an output schema, it covers every action (list, busy, create, update, remove) including defaults and window caps, delete confirmation behavior, and editability limits. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds genuinely non-obvious meaning: starts_at alone on update preserves duration, reminder_minutes=0 is intended for short reminder blocks, and request_id should only be reused on retry of the same block. It doesn't add syntax details for from/to beyond the schema, so not a 5.

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?

States a specific verb and resource: 'Manage personal Google/Outlook calendar blocks with no attendees', and immediately delimits scope ('nothing is sent'). An agent can distinguish this from meeting-oriented siblings like find_times or propose_meeting without opening the schema.

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?

Explicitly says when to use it ('Block focus time in a free gap, add reminders, or adjust your own blocks') and names the alternative for the other case ('use find_times for meetings with others'). The busy action is also framed as the way to find a free gap, which is a concrete routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources