LobbyStack

Replace opening hours

update_business_hours

DestructiveIdempotent

Replaces the whole week of opening hours. Send every day that should be open; any day you leave out becomes closed. Read the current hours with get_business first and change only what the owner asked for. Times are in the business time zone. Returns the updated business.

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": {
      "hours": "<hours>"
    },
    "name": "update_business_hours"
  }
}

Input Schema

Name	Required	Description	Default
`hours`	Yes	One entry per opening window. A day with a break, such as lunch, has two entries. An empty list closes the business every day.

Output Schema

Name	Required	Description
`id`	Yes	Stable identifier (UUID).
`name`	Yes
`hours`	Yes
`locale`	Yes	Default language for callers: en, fr, es, sr (Serbian, Latin script), de, pt (Brazilian Portuguese), it, nl, pl, tr, vi, tl (Tagalog), sv, ru or uk.
`timezone`	Yes	IANA time zone, for example America/Toronto.
`created_at`	Yes	ISO 8601 timestamp in UTC.
`updated_at`	Yes	ISO 8601 timestamp in UTC.
`website_url`	Yes
`booking_mode`	Yes	instant: appointments are booked directly. request: the receptionist takes a request and the team confirms it. off: no booking.
`business_type`	Yes	What kind of business it is. The dashboard uses service_company.
`onboarding_stage`	Yes	Where the business is in onboarding, for example website, phone_number or complete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description explains the exact mechanism of destruction (omitted days become closed, empty-equivalent behavior implied by whole-week replacement) plus the time-zone basis for all times. That is precisely the context annotations cannot convey.

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, each with a distinct job: what it does, the omission consequence, the prerequisite, and the time-zone/return note. Destructive semantics are front-loaded ahead of the workflow advice.

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 single-parameter, mutation tool with an output schema present, the description covers the destructive scope, the recommended read-first workflow, time-zone semantics, and the return value at a glance. Nothing an agent needs before calling it 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 description coverage is 100%, so the baseline is 3; the description goes slightly beyond by framing the array as 'every day that should be open' and by grounding all times in the business time zone. It does not add format or break-window detail beyond what the schema already documents.

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, 'Replaces the whole week of opening hours,' and immediately defines the replacement semantics (full-week overwrite rather than per-day patch). An agent can tell exactly what this tool does and what scope of data it touches.

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?

Gives an explicit prerequisite workflow: read current hours with the named sibling get_business first, then apply only the owner's requested change. It also warns that any day left out becomes closed, which is a strong when-not-to-omit constraint rather than generic advice.

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

All LobbyStack tools Inspect

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

Need Help?