Skip to main content
Glama

update_booking_settings

Idempotent

Update an existing booking page's hours, time zone, default duration and availability. Supply the full settings and optionally the customer change notice.

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": {
      "timezone": "<timezone>",
      "weekdays": "<weekdays>",
      "opens": "<opens>",
      "closes": "<closes>",
      "durationMinutes": "<durationMinutes>",
      "enabled": "<enabled>"
    },
    "name": "update_booking_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
opensYes
closesYes
enabledYes
timezoneYes
weekdaysYes
durationMinutesYes
changeNoticeHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuinely useful trait beyond that: the full settings must be supplied, implying overwrite semantics for omitted fields. It says nothing about permissions, validation failures, or what the customer notice actually triggers.

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?

Two tight sentences, front-loaded with the verb and resource, with the replacement constraint and optional parameter called out in the second sentence. No filler, though the field list could be ordered to match the required schema fields.

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

Completeness3/5

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

For a 6-required-parameter mutation with no output schema, the description covers the main concepts and the full-replace behavior, but leaves gaps: the units/ranges for duration, the meaning of enabled, and whether unsupplied optional fields are cleared. Annotations cover safety, so the remaining gap is moderate rather than severe.

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 0% across 7 parameters, so the description has to carry the meaning. It maps timezone, opens/closes ('hours'), durationMinutes ('default duration') and weekdays/enabled ('availability') to plain concepts, and flags changeNoticeHours as an optional customer notice. It still leaves the enabled flag and the change-notice lead-time meaning implicit.

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

Purpose4/5

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

States a specific verb (Update) and resource (an existing booking page's settings) plus the fields affected: hours, time zone, default duration, availability. It is clearly distinct from get_booking_settings and the other settings updaters, though it does not name any sibling explicitly.

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

Usage Guidelines3/5

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

The phrase 'Supply the full settings' implies this is a full-replacement update rather than a partial patch, which is useful usage context. However, it never states when to call this versus get_booking_settings first, nor whether reading current settings is a prerequisite before overwriting them.

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