Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Set my booking hours

connections_schedule_set_booking_hours
Destructive

Set the member's weekly booking hours (availability) and optionally the page's time zone. This replaces the whole week, so every window must be sent: Monday to Friday 9 to 5 is five windows. Link, meeting types, prices and time-off days are unchanged. The current hours and time zone are returned by get_booking_setup. When the chat is pinned to a workspace it sets that workspace's page.

Input Schema

NameRequiredDescriptionDefault
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
dry_runNoPreview only.
projectNoWorkspace to run this call in (id or name).
windowsYesEvery bookable window in the week. A day with a lunch break is two windows.
timeZoneNoOptional. IANA time zone, e.g. America/Los_Angeles; omit to keep the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only; nothing is written."New value: +"Preview only."
  2. Changed5 schema fields changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: return what this call would do, with nothing written."New value: +"Preview only; nothing is written."
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
    • changedInput schema / properties / timeZone / description
      Previous value: -"Optional. An IANA time zone name such as America/Los_Angeles or Europe/London. Leave it out to keep the page's current time zone."New value: +"Optional. IANA time zone, e.g. America/Los_Angeles; omit to keep the current one."
    • changedInput schema / properties / windows / items / properties / endTime / description
      Previous value: -"When booking closes that day, 24-hour HH:mm, e.g. 17:00. After the start."New value: +"Closing time, 24-hour HH:mm, after the start."
    • changedInput schema / properties / windows / items / properties / startTime / description
      Previous value: -"When booking opens that day, 24-hour HH:mm, e.g. 09:00."New value: +"Opening time, 24-hour HH:mm."
  3. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description earns its keep by explaining exactly what the destruction means: full-week replacement, so any omitted window is lost, and a concrete example of five windows for Mon–Fri 9–5. It also enumerates what is preserved (link, meeting types, prices, time-off days), which is precisely the reassurance an agent needs before overwriting availability.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action and the replacement warning, then the preservation list, then the read-path pointer. The 'Monday to Friday 9 to 5 is five windows' example is concrete rather than filler; nothing is redundant with the schema or annotations.

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?

For a destructive mutation with no output schema, the description covers scope, preservation, prerequisites and per-call targeting. The only mild gap is that it never says what the call itself returns on success (only that get_booking_setup returns current state), which leaves the agent guessing about confirmation output.

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 real semantic weight: 'windows' is a complete replacement set rather than an append, and a lunch break must be modeled as two windows. That meaning is not in the schema and directly affects how the array is constructed.

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: 'Set the member's weekly booking hours (availability)' plus optional time zone. It also contrasts itself with the read path by naming get_booking_setup, so an agent can tell which of the pair to call without inspecting either schema.

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

Usage Guidelines4/5

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

Gives a clear usage condition — send every window because the whole week is replaced — and routes the agent to get_booking_setup to read the current state first. It also clarifies the workspace-pinned case. It stops short of explicit exclusions (e.g. what to use for one-off availability changes or time-off), so a 4 rather than a 5.

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

All Connections toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources