Skip to main content
Glama

save_booking_schedule

Replace a staff or resource schedule. Supply its current revision, or null when it has no saved schedule. Hours follow the business time zone.

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": {
      "kind": "<kind>",
      "targetId": "<targetId>",
      "schedule": "<schedule>"
    },
    "name": "save_booking_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
scheduleYes
targetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false, openWorld=false), so the bar is lower. The description adds genuinely new behavior: this is a full replacement rather than a patch, it is guarded by a revision token (implying stale-revision rejection), and hour values are interpreted in the business time zone. It does not state what the failure mode looks like on a revision mismatch, which is the one behavior an agent most needs to handle.

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?

Three short sentences with no filler; the replacement action and the revision rule are front-loaded before the time zone note. Every sentence carries information the schema does not.

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 3-parameter, deeply nested write tool with no output schema and zero schema descriptions, the definition covers the concurrency contract and time zone but leaves the nested schedule structure (weeklyHours slot ordering, null-means-closed, timeOff datetime format) undocumented. An agent could construct a well-formed revision but a plausible-but-wrong weeklyHours payload.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load, and it only partially does. It explains revision semantics (uuid vs null) and the time zone of hour values, but says nothing about targetId beyond the entity kind, and nothing about weeklyHours being a fixed 7-slot array where null means closed, or the local-datetime format and 50-item cap on timeOff.

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?

The description opens with a specific verb and resource: 'Replace a staff or resource schedule,' and the enum in the schema confirms the two entity kinds. This distinguishes it from read-oriented siblings like list_booking_schedules, but it never names an alternative tool or states the boundary explicitly, so sibling differentiation is only implied by the write verb.

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?

It gives a concrete prerequisite that governs correct invocation: pass the current revision, or null when no schedule exists yet. That is real usage guidance for the trickiest part of the call. It stops short of saying when to prefer this over other save/update tools or what to do when a revision conflict occurs.

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